Project Number Date
test_Tails_ISO_devel 4595 04 Sep 2026, 07:39

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 11:24.115 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:1.362
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.092
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.441
When I start Tails from USB drive "old" with network unplugged 44.198
Then the boot device has safe access rights 2.069
And Tails is running from USB drive "old" 0.166
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.029
And udev-watchdog is monitoring the correct device 0.154
And I unplug USB drive "old" 0.124
After features/support/hooks.rb:339 3.695
After features/support/hooks.rb:108 0.010
Tags: @product
1:21.687
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.085
And I start Tails from USB drive "old" with network unplugged and I login 47.722
Then Tails is running from USB drive "old" 0.218
And I create a persistent partition 22.620
And I take note of which tps features are available 6.364
Then a Tails persistence partition exists on USB drive "old" 0.532
And I shutdown Tails and wait for the computer to power off 4.143
After features/support/hooks.rb:339 0.154
After features/support/hooks.rb:108 0.005
Tags: @product
1:34.168
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.091
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.327
Then Tails is running from USB drive "old" 0.158
And all tps features are active 8.316
When I write some files expected to persist 1.213
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.190
And all persistence configuration files have safe access rights 0.288
And all persistent directories from the old Tails version have safe access rights 1.737
And I take note of which tps features are available 6.412
And I shutdown Tails and wait for the computer to power off 4.108
# 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" 11.323
After features/support/hooks.rb:339 0.171
After features/support/hooks.rb:108 0.006
Tags: @product
2:25.008
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 21.241
And I log in to a new session 11.338
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.671
And I plug USB drive "to_upgrade" 2.192
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.811
Then the running Tails is installed on USB drive "to_upgrade" 18.499
And I unplug USB drive "to_upgrade" 0.135
And I unplug USB drive "__internal" 0.119
After features/support/hooks.rb:339 1.688
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.373
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given a computer 0.085
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.227
Then all tps features from the old Tails version are active 1.060
And Tails is running from USB drive "to_upgrade" 0.224
And the boot device has safe access rights 2.241
And the expected persistent files created with the old Tails version are present in the filesystem 0.940
And all persistent directories from the old Tails version have safe access rights 1.592
After features/support/hooks.rb:339 0.862
After features/support/hooks.rb:108 0.034
Tags: @product @automatic_upgrade
3:32.146
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 8.127
And no SquashFS delta is installed 0.097
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.198
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.262
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.473
When the network is plugged 0.036
And Tor is ready 13.477
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.293
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.745
Given I shutdown Tails and wait for the computer to power off 5.468
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.441
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 8.393
And the file system changes introduced in version 6.2~testoverlayfs are present 0.288
And only the 6.2~testoverlayfs SquashFS delta is installed 0.044
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.124
# 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.153
When the network is plugged 0.022
And Tor is ready 10.369
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.868
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.734
Given I shutdown Tails and wait for the computer to power off 2.532
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.764
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 9.992
And the file system changes introduced in version 6.3~testoverlayfs are present 0.372
And only the 6.3~testoverlayfs SquashFS delta is installed 0.056
# 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.160
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.212
When the network is plugged 0.028
And Tor is ready 10.211
Then the Upgrader considers the system as up-to-date 0.083
# 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 3.746
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.296
After features/support/hooks.rb:339 0.862
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
19.368
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.907
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.229
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.034
And the signing key used by the Upgrader is outdated 0.035
But a current signing key is available on our website 0.000
When the network is plugged 0.029
And Tor is ready 10.236
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.896
After features/support/hooks.rb:339 0.794
After features/support/hooks.rb:108 0.000