Project Number Date
test_Tails_ISO_21651-persist-gnome-software-based-on-17367 2 05 Aug 2026, 09:18

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:39.760 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:9.423
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.047
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 13.133
When I start Tails from USB drive "old" with network unplugged 52.057
Then the boot device has safe access rights 2.398
And Tails is running from USB drive "old" 0.237
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.077
And udev-watchdog is monitoring the correct device 0.246
And I unplug USB drive "old" 0.155
After features/support/hooks.rb:339 1.620
After features/support/hooks.rb:108 0.005
Tags: @product
1:24.896
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.050
And I start Tails from USB drive "old" with network unplugged and I login 52.417
Then Tails is running from USB drive "old" 0.267
And I create a persistent partition 23.607
And I take note of which tps features are available 4.118
Then a Tails persistence partition exists on USB drive "old" 0.483
And I shutdown Tails and wait for the computer to power off 3.951
After features/support/hooks.rb:339 0.427
After features/support/hooks.rb:108 0.006
Tags: @product
1:31.789
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.050
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.216
Then Tails is running from USB drive "old" 0.239
And all tps features are active 4.949
When I write some files expected to persist 1.252
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.158
And all persistence configuration files have safe access rights 0.267
And all persistent directories from the old Tails version have safe access rights 1.888
And I take note of which tps features are available 3.674
And I shutdown Tails and wait for the computer to power off 4.084
# 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.007
After features/support/hooks.rb:339 0.573
After features/support/hooks.rb:108 0.006
Tags: @product
2:9.102
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 8.099
And I log in to a new session 12.509
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.754
And I plug USB drive "to_upgrade" 2.209
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.289
Then the running Tails is installed on USB drive "to_upgrade" 13.953
And I unplug USB drive "to_upgrade" 0.145
And I unplug USB drive "__internal" 0.141
After features/support/hooks.rb:339 2.419
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.734
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.051
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.965
Then all tps features from the old Tails version are active 1.107
And Tails is running from USB drive "to_upgrade" 0.249
And the boot device has safe access rights 2.439
And the expected persistent files created with the old Tails version are present in the filesystem 1.152
And all persistent directories from the old Tails version have safe access rights 1.769
After features/support/hooks.rb:339 1.000
After features/support/hooks.rb:108 0.024
Tags: @product @automatic_upgrade
3:52.510
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.767
And no SquashFS delta is installed 0.072
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.270
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.227
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.353
When the network is plugged 0.019
And Tor is ready 13.984
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.366
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.501
Given I shutdown Tails and wait for the computer to power off 6.984
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.580
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 6.339
And the file system changes introduced in version 6.2~testoverlayfs are present 0.232
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.110
# 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.239
When the network is plugged 0.017
And Tor is ready 12.349
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.732
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.867
Given I shutdown Tails and wait for the computer to power off 4.006
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.330
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 6.002
And the file system changes introduced in version 6.3~testoverlayfs are present 0.304
And only the 6.3~testoverlayfs SquashFS delta is installed 0.047
# 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.153
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.178
When the network is plugged 0.012
And Tor is ready 10.177
Then the Upgrader considers the system as up-to-date 10.503
# 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.280
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.373
After features/support/hooks.rb:339 0.895
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
21.302
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.285
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.210
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
And the signing key used by the Upgrader is outdated 0.040
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 9.953
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.756
After features/support/hooks.rb:339 0.963
After features/support/hooks.rb:108 0.000