Project Number Date
test_Tails_ISO_stable 4823 02 May 2024, 13:24

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:36.718 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:29.864
Before features/support/hooks.rb:259 0.005
Given a computer 0.464
And I create a 7200 MiB disk named "old" 0.254
And I plug USB drive "old" 1.116
And I write an old version of the Tails USB image to disk "old" 53.643
When I start Tails from USB drive "old" with network unplugged 1:30.093
Then the boot device has safe access rights 3.227
And Tails is running from USB drive "old" 0.355
And there is no persistence partition on USB drive "old" 0.055
And process "udev-watchdog" is running 0.125
And udev-watchdog is monitoring the correct device 0.343
And I unplug USB drive "old" 0.186
After features/support/hooks.rb:305 4.023
After features/support/hooks.rb:89 0.012
Tags: @product
2:22.231
Before features/support/hooks.rb:259 0.007
Given a computer 0.329
And I start Tails from USB drive "old" with network unplugged and I login 1:28.994
Then Tails is running from USB drive "old" 0.402
And I create a persistent partition 40.571
And I take note of which tps features are available 1.682
Then a Tails persistence partition exists on USB drive "old" 0.974
And I shutdown Tails and wait for the computer to power off 9.275
After features/support/hooks.rb:305 0.203
After features/support/hooks.rb:89 0.036
Tags: @product
3:8.858
Before features/support/hooks.rb:259 0.007
Given a computer 0.286
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:29.859
Then Tails is running from USB drive "old" 0.624
And all tps features are active 2.269
When I write some files expected to persist 2.151
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.244
And all persistence configuration files have safe access rights 0.392
And all persistent directories from the old Tails version have safe access rights 2.593
And I take note of which tps features are available 0.852
And I shutdown Tails and wait for the computer to power off 4.509
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.075
After features/support/hooks.rb:305 0.163
After features/support/hooks.rb:89 0.009
Tags: @product
3:4.066
Before features/support/hooks.rb:259 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 35.377
And I log in to a new session 18.138
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.728
And I plug USB drive "to_upgrade" 2.465
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:43.453
Then the running Tails is installed on USB drive "to_upgrade" 21.452
And I unplug USB drive "to_upgrade" 0.264
And I unplug USB drive "__internal" 0.185
After features/support/hooks.rb:305 2.272
After features/support/hooks.rb:89 0.000
Tags: @product
2:12.564
Before features/support/hooks.rb:259 0.005
Given a computer 0.681
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.888
Then all tps features from the old Tails version are active 1.546
And Tails is running from USB drive "to_upgrade" 0.285
And the boot device has safe access rights 3.227
And the expected persistent files created with the old Tails version are present in the filesystem 1.538
And all persistent directories from the old Tails version have safe access rights 2.395
After features/support/hooks.rb:305 0.828
After features/support/hooks.rb:89 0.009
Tags: @product @automatic_upgrade
6:37.975
Before features/support/hooks.rb:259 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.681
And no SquashFS delta is installed 1.061
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.387
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.281
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.462
When the network is plugged 0.031
And Tor is ready 21.193
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.378
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.590
Given I shutdown Tails and wait for the computer to power off 8.572
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.043
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.062
And the file system changes introduced in version 6.2~testoverlayfs are present 0.301
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.379
# 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.261
When the network is plugged 0.035
And Tor is ready 19.969
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.825
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.774
Given I shutdown Tails and wait for the computer to power off 4.679
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.611
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.816
And the file system changes introduced in version 6.3~testoverlayfs are present 0.707
And only the 6.3~testoverlayfs SquashFS delta is installed 0.090
# 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.359
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.361
When the network is plugged 0.047
And Tor is ready 19.090
Then the Upgrader considers the system as up-to-date 0.340
# 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 17.213
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.204
After features/support/hooks.rb:305 0.801
After features/support/hooks.rb:89 0.028
Tags: @product @automatic_upgrade
41.158
Before features/support/hooks.rb:259 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.928
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.354
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.140
And the signing key used by the Upgrader is outdated 0.711
But a current signing key is available on our website 0.000
When the network is plugged 0.050
And Tor is ready 18.272
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.700
After features/support/hooks.rb:305 0.956
After features/support/hooks.rb:89 0.000