Project Number Date
test_Tails_ISO_stable 5046 26 Aug 2024, 12:34

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 18:55.694 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:11.523
Before features/support/hooks.rb:269 0.005
Given a computer 0.189
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 31.933
When I start Tails from USB drive "old" with network unplugged 1:34.075
Then the boot device has safe access rights 3.180
And Tails is running from USB drive "old" 0.361
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.326
And I unplug USB drive "old" 0.192
After features/support/hooks.rb:326 7.012
After features/support/hooks.rb:100 0.008
Tags: @product
2:5.845
Before features/support/hooks.rb:269 0.004
Given a computer 0.231
And I start Tails from USB drive "old" with network unplugged and I login 1:22.241
Then Tails is running from USB drive "old" 0.332
And I create a persistent partition 32.254
And I take note of which tps features are available 1.589
Then a Tails persistence partition exists on USB drive "old" 0.892
And I shutdown Tails and wait for the computer to power off 8.302
After features/support/hooks.rb:326 0.180
After features/support/hooks.rb:100 0.009
Tags: @product
2:56.740
Before features/support/hooks.rb:269 0.006
Given a computer 0.264
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.991
Then Tails is running from USB drive "old" 0.341
And all tps features are active 2.511
When I write some files expected to persist 1.969
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.227
And all persistence configuration files have safe access rights 0.423
And all persistent directories from the old Tails version have safe access rights 2.750
And I take note of which tps features are available 0.518
And I shutdown Tails and wait for the computer to power off 4.425
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.316
After features/support/hooks.rb:326 0.124
After features/support/hooks.rb:100 0.009
Tags: @product
2:29.613
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 11.957
And I log in to a new session 18.344
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.679
And I plug USB drive "to_upgrade" 2.430
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.423
Then the running Tails is installed on USB drive "to_upgrade" 20.273
And I unplug USB drive "to_upgrade" 0.231
And I unplug USB drive "__internal" 0.273
After features/support/hooks.rb:326 2.449
After features/support/hooks.rb:100 0.000
Tags: @product
2:11.347
Before features/support/hooks.rb:269 0.007
Given a computer 0.194
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.614
Then all tps features from the old Tails version are active 1.618
And Tails is running from USB drive "to_upgrade" 0.330
And the boot device has safe access rights 3.546
And the expected persistent files created with the old Tails version are present in the filesystem 1.466
And all persistent directories from the old Tails version have safe access rights 2.576
After features/support/hooks.rb:326 0.767
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:21.773
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 13.619
And no SquashFS delta is installed 0.078
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.348
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.077
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.301
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.478
When the network is plugged 0.078
And Tor is ready 22.400
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.071
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.033
Given I shutdown Tails and wait for the computer to power off 10.939
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.048
Then Tails is running version 6.2~testoverlayfs 0.046
And all tps features are active 2.195
And the file system changes introduced in version 6.2~testoverlayfs are present 0.327
And only the 6.2~testoverlayfs SquashFS delta is installed 0.128
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.323
# 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.075
And Tor is ready 20.217
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.250
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.830
Given I shutdown Tails and wait for the computer to power off 4.317
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.849
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.226
And the file system changes introduced in version 6.3~testoverlayfs are present 0.432
And only the 6.3~testoverlayfs SquashFS delta is installed 0.074
# 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.316
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.264
When the network is plugged 0.078
And Tor is ready 19.292
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 14.374
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.075
After features/support/hooks.rb:326 0.757
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
38.851
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 10.683
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.268
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.736
But a current signing key is available on our website 0.000
When the network is plugged 0.101
And Tor is ready 20.318
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.681
After features/support/hooks.rb:326 0.758
After features/support/hooks.rb:100 0.000