Project Number Date
test_Tails_ISO_devel 4498 17 Jul 2026, 11:29

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 87 0 0 0 0 87 7 0 7 12:28.732 Passed
Tags: @product
Feature Upgrading an old Tails USB installation
As a Tails user If I have an old version of Tails installed on a USB device and the USB device has a Persistent Storage I want to upgrade Tails on it and keep my Persistent Storage in the process
Tags: @product
1:12.477
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.068
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 14.281
When I start Tails from USB drive "old" with network unplugged 53.540
Then the boot device has safe access rights 2.874
And Tails is running from USB drive "old" 0.225
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.067
And udev-watchdog is monitoring the correct device 0.183
And I unplug USB drive "old" 0.141
After features/support/hooks.rb:339 3.604
After features/support/hooks.rb:108 0.007
Tags: @product
1:36.398
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.084
And I start Tails from USB drive "old" with network unplugged and I login 57.081
Then Tails is running from USB drive "old" 0.245
And I create a persistent partition 25.589
And I take note of which tps features are available 4.737
Then a Tails persistence partition exists on USB drive "old" 0.559
And I shutdown Tails and wait for the computer to power off 8.099
After features/support/hooks.rb:339 0.489
After features/support/hooks.rb:108 0.006
Tags: @product
1:42.825
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.060
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:7.762
Then Tails is running from USB drive "old" 0.230
And all tps features are active 5.955
When I write some files expected to persist 1.537
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.160
And all persistence configuration files have safe access rights 0.375
And all persistent directories from the old Tails version have safe access rights 2.019
And I take note of which tps features are available 4.169
And I shutdown Tails and wait for the computer to power off 8.386
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 12.167
After features/support/hooks.rb:339 0.574
After features/support/hooks.rb:108 0.007
Tags: @product
2:12.532
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 7.829
And I log in to a new session 12.655
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.832
And I plug USB drive "to_upgrade" 2.220
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.675
Then the running Tails is installed on USB drive "to_upgrade" 16.047
And I unplug USB drive "to_upgrade" 0.136
And I unplug USB drive "__internal" 0.134
After features/support/hooks.rb:339 2.347
After features/support/hooks.rb:108 0.000
Tags: @product
1:16.684
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.060
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.786
Then all tps features from the old Tails version are active 1.217
And Tails is running from USB drive "to_upgrade" 0.415
And the boot device has safe access rights 2.819
And the expected persistent files created with the old Tails version are present in the filesystem 1.312
And all persistent directories from the old Tails version have safe access rights 2.071
After features/support/hooks.rb:339 0.607
After features/support/hooks.rb:108 0.007
Tags: @product @automatic_upgrade
4:7.322
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.566
And no SquashFS delta is installed 0.065
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.251
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.239
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.373
When the network is plugged 0.018
And Tor is ready 13.391
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.466
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.668
Given I shutdown Tails and wait for the computer to power off 7.097
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.324
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 5.683
And the file system changes introduced in version 6.2~testoverlayfs are present 0.260
And only the 6.2~testoverlayfs SquashFS delta is installed 0.049
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.162
# We'll really install Tails_amd64_6.0~testoverlayfs_to_6.3~testoverlayfs.iuk
# but we need some way to force upgrading a second time in a row
# even if only the initially installed version is considered
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.258
When the network is plugged 0.020
And Tor is ready 9.992
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.432
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.748
Given I shutdown Tails and wait for the computer to power off 8.387
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.785
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 5.988
And the file system changes introduced in version 6.3~testoverlayfs are present 0.441
And only the 6.3~testoverlayfs SquashFS delta is installed 0.061
# Regression test for #17425 (i.e. the Upgrader would propose
# upgrading to the version that's already running)
Given Tails system time is magically synchronized 0.133
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.230
When the network is plugged 0.075
And Tor is ready 10.711
Then the Upgrader considers the system as up-to-date 10.577
# Regression test on #8158 (i.e. the IUK's filesystem is not part of the Unsafe Browser's chroot)
And I successfully start the Unsafe Browser 4.398
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.372
After features/support/hooks.rb:339 0.777
After features/support/hooks.rb:108 0.022
Tags: @product @automatic_upgrade
20.491
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.366
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.249
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 0.053
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 9.449
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.295
After features/support/hooks.rb:339 0.750
After features/support/hooks.rb:108 0.000