Project Number Date
test_Tails_ISO_stable 5519 17 Mar 2025, 17:05

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 19:52.667 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:19.049
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.181
And I create a 7200 MiB disk named "old" 0.068
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 33.258
When I start Tails from USB drive "old" with network unplugged 1:40.359
Then the boot device has safe access rights 3.092
And Tails is running from USB drive "old" 0.340
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.298
And I unplug USB drive "old" 0.231
After features/support/hooks.rb:330 3.594
After features/support/hooks.rb:100 0.011
Tags: @product
2:12.760
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.279
And I start Tails from USB drive "old" with network unplugged and I login 1:29.989
Then Tails is running from USB drive "old" 0.330
And I create a persistent partition 31.262
And I take note of which tps features are available 1.452
Then a Tails persistence partition exists on USB drive "old" 0.814
And I shutdown Tails and wait for the computer to power off 8.631
After features/support/hooks.rb:330 0.155
After features/support/hooks.rb:100 0.009
Tags: @product
2:58.904
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.255
Then Tails is running from USB drive "old" 0.366
And all tps features are active 1.866
When I write some files expected to persist 1.885
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.199
And all persistence configuration files have safe access rights 0.405
And all persistent directories from the old Tails version have safe access rights 2.998
And I take note of which tps features are available 0.452
And I shutdown Tails and wait for the computer to power off 4.467
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.809
After features/support/hooks.rb:330 0.116
After features/support/hooks.rb:100 0.011
Tags: @product
2:28.636
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 without a persistent partition and stopped at Tails Greeter's login screen 11.099
And I log in to a new session 19.109
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.290
And I plug USB drive "to_upgrade" 2.471
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.862
Then the running Tails is installed on USB drive "to_upgrade" 19.322
And I unplug USB drive "to_upgrade" 0.227
And I unplug USB drive "__internal" 0.253
After features/support/hooks.rb:330 2.726
After features/support/hooks.rb:100 0.000
Tags: @product
2:22.975
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.268
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.730
Then all tps features from the old Tails version are active 1.830
And Tails is running from USB drive "to_upgrade" 0.360
And the boot device has safe access rights 3.605
And the expected persistent files created with the old Tails version are present in the filesystem 1.600
And all persistent directories from the old Tails version have safe access rights 2.580
After features/support/hooks.rb:330 1.237
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:32.234
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 11.900
And no SquashFS delta is installed 0.266
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.452
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.347
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.546
When the network is plugged 0.065
And Tor is ready 19.465
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.873
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.783
Given I shutdown Tails and wait for the computer to power off 8.714
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.889
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 2.098
And the file system changes introduced in version 6.2~testoverlayfs are present 0.319
And only the 6.2~testoverlayfs SquashFS delta is installed 0.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.297
# 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.286
When the network is plugged 0.069
And Tor is ready 18.897
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.693
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.313
Given I shutdown Tails and wait for the computer to power off 4.409
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.559
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.280
And the file system changes introduced in version 6.3~testoverlayfs are present 0.563
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.292
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.323
When the network is plugged 0.070
And Tor is ready 20.644
Then the Upgrader considers the system as up-to-date 0.318
# 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.301
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.939
After features/support/hooks.rb:330 0.971
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
58.105
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 9.985
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.750
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.105
And the signing key used by the Upgrader is outdated 0.113
But a current signing key is available on our website 0.000
When the network is plugged 0.084
And Tor is ready 46.469
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.596
After features/support/hooks.rb:330 1.064
After features/support/hooks.rb:100 0.000