Project Number Date
test_Tails_ISO_stable 5680 28 May 2025, 09:14

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 20:41.221 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
2:21.936
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.023
Given a computer 0.366
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 38.195
When I start Tails from USB drive "old" with network unplugged 1:37.637
Then the boot device has safe access rights 3.601
And Tails is running from USB drive "old" 0.363
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.095
And udev-watchdog is monitoring the correct device 0.297
And I unplug USB drive "old" 0.211
After features/support/hooks.rb:330 7.131
After features/support/hooks.rb:100 0.010
Tags: @product
2:21.010
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.230
And I start Tails from USB drive "old" with network unplugged and I login 1:34.746
Then Tails is running from USB drive "old" 0.402
And I create a persistent partition 33.867
And I take note of which tps features are available 2.601
Then a Tails persistence partition exists on USB drive "old" 0.839
And I shutdown Tails and wait for the computer to power off 8.322
After features/support/hooks.rb:330 0.206
After features/support/hooks.rb:100 0.010
Tags: @product
3:14.875
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.197
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:32.654
Then Tails is running from USB drive "old" 0.389
And all tps features are active 2.412
When I write some files expected to persist 1.726
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.228
And all persistence configuration files have safe access rights 0.358
And all persistent directories from the old Tails version have safe access rights 3.165
And I take note of which tps features are available 2.923
And I shutdown Tails and wait for the computer to power off 6.194
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.624
After features/support/hooks.rb:330 0.132
After features/support/hooks.rb:100 0.010
Tags: @product
2:43.171
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.626
And I log in to a new session 21.116
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.015
And I plug USB drive "to_upgrade" 2.487
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.826
Then the running Tails is installed on USB drive "to_upgrade" 26.633
And I unplug USB drive "to_upgrade" 0.239
And I unplug USB drive "__internal" 0.226
After features/support/hooks.rb:330 2.788
After features/support/hooks.rb:100 0.000
Tags: @product
2:23.176
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.311
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.446
Then all tps features from the old Tails version are active 1.875
And Tails is running from USB drive "to_upgrade" 0.352
And the boot device has safe access rights 3.981
And the expected persistent files created with the old Tails version are present in the filesystem 1.571
And all persistent directories from the old Tails version have safe access rights 2.637
After features/support/hooks.rb:330 1.376
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:58.016
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.579
And no SquashFS delta is installed 0.356
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.540
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.075
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.443
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.467
When the network is plugged 0.091
And Tor is ready 50.174
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.777
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.153
Given I shutdown Tails and wait for the computer to power off 9.013
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.580
Then Tails is running version 6.2~testoverlayfs 0.021
And all tps features are active 2.352
And the file system changes introduced in version 6.2~testoverlayfs are present 0.317
And only the 6.2~testoverlayfs SquashFS delta is installed 0.076
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.315
# 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.310
When the network is plugged 0.076
And Tor is ready 15.749
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.392
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.113
Given I shutdown Tails and wait for the computer to power off 4.375
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.414
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.225
And the file system changes introduced in version 6.3~testoverlayfs are present 0.538
And only the 6.3~testoverlayfs SquashFS delta is installed 0.077
# 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.398
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.286
When the network is plugged 0.133
And Tor is ready 16.851
Then the Upgrader considers the system as up-to-date 0.309
# 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 15.715
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.694
After features/support/hooks.rb:330 0.800
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
39.032
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.928
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.722
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.151
And the signing key used by the Upgrader is outdated 0.242
But a current signing key is available on our website 0.000
When the network is plugged 0.134
And Tor is ready 20.085
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.767
After features/support/hooks.rb:330 1.395
After features/support/hooks.rb:100 0.000