Project Number Date
test_Tails_ISO_stable 5453 12 Feb 2025, 13:06

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 22:47.065 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:28.448
Before features/support/hooks.rb:269 0.004
Given a computer 0.261
And I create a 7200 MiB disk named "old" 0.074
And I plug USB drive "old" 1.057
And I write an old version of the Tails USB image to disk "old" 50.694
When I start Tails from USB drive "old" with network unplugged 1:31.768
Then the boot device has safe access rights 3.453
And Tails is running from USB drive "old" 0.428
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.106
And udev-watchdog is monitoring the correct device 0.326
And I unplug USB drive "old" 0.206
After features/support/hooks.rb:326 3.925
After features/support/hooks.rb:100 0.012
Tags: @product
2:22.451
Before features/support/hooks.rb:269 0.006
Given a computer 0.353
And I start Tails from USB drive "old" with network unplugged and I login 1:32.541
Then Tails is running from USB drive "old" 0.361
And I create a persistent partition 35.524
And I take note of which tps features are available 3.879
Then a Tails persistence partition exists on USB drive "old" 0.918
And I shutdown Tails and wait for the computer to power off 8.872
After features/support/hooks.rb:326 0.312
After features/support/hooks.rb:100 0.010
Tags: @product
3:16.854
Before features/support/hooks.rb:269 0.007
Given a computer 0.292
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:34.382
Then Tails is running from USB drive "old" 0.556
And all tps features are active 2.815
When I write some files expected to persist 2.281
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.264
And all persistence configuration files have safe access rights 0.457
And all persistent directories from the old Tails version have safe access rights 2.681
And I take note of which tps features are available 0.623
And I shutdown Tails and wait for the computer to power off 4.382
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 28.117
After features/support/hooks.rb:326 0.208
After features/support/hooks.rb:100 0.016
Tags: @product
2:46.304
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.849
And I log in to a new session 20.309
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.098
And I plug USB drive "to_upgrade" 2.521
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.786
Then the running Tails is installed on USB drive "to_upgrade" 28.240
And I unplug USB drive "to_upgrade" 0.270
And I unplug USB drive "__internal" 0.227
After features/support/hooks.rb:326 3.585
After features/support/hooks.rb:100 0.000
Tags: @product
2:35.475
Before features/support/hooks.rb:269 0.008
Given a computer 0.294
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:22.395
Then all tps features from the old Tails version are active 4.810
And Tails is running from USB drive "to_upgrade" 0.327
And the boot device has safe access rights 3.328
And the expected persistent files created with the old Tails version are present in the filesystem 1.618
And all persistent directories from the old Tails version have safe access rights 2.700
After features/support/hooks.rb:326 1.076
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
8:35.537
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 24.971
And no SquashFS delta is installed 0.132
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.304
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.460
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.588
When the network is plugged 0.098
And Tor is ready 22.505
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.105
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.943
Given I shutdown Tails and wait for the computer to power off 1:30.696
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.945
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.652
And the file system changes introduced in version 6.2~testoverlayfs are present 0.328
And only the 6.2~testoverlayfs SquashFS delta is installed 0.082
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.338
# 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.459
When the network is plugged 0.089
And Tor is ready 21.136
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.121
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.775
Given I shutdown Tails and wait for the computer to power off 4.393
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:17.911
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 5.845
And the file system changes introduced in version 6.3~testoverlayfs are present 0.551
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.387
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.340
When the network is plugged 0.333
And Tor is ready 19.285
Then the Upgrader considers the system as up-to-date 0.408
# 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 14.958
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.219
After features/support/hooks.rb:326 1.020
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
41.993
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.291
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.475
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.090
And the signing key used by the Upgrader is outdated 0.142
But a current signing key is available on our website 0.000
When the network is plugged 0.133
And Tor is ready 19.703
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.155
After features/support/hooks.rb:326 1.740
After features/support/hooks.rb:100 0.000