Project Number Date
test_Tails_ISO_stable 5004 07 Aug 2024, 12:43

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:59.934 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:31.375
Before features/support/hooks.rb:269 0.007
Given a computer 0.277
And I create a 7200 MiB disk named "old" 0.352
And I plug USB drive "old" 1.175
And I write an old version of the Tails USB image to disk "old" 32.082
When I start Tails from USB drive "old" with network unplugged 1:53.445
Then the boot device has safe access rights 3.009
And Tails is running from USB drive "old" 0.381
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.088
And udev-watchdog is monitoring the correct device 0.316
And I unplug USB drive "old" 0.181
After features/support/hooks.rb:326 3.497
After features/support/hooks.rb:100 0.026
Tags: @product
2:15.287
Before features/support/hooks.rb:269 0.007
Given a computer 0.191
And I start Tails from USB drive "old" with network unplugged and I login 1:30.801
Then Tails is running from USB drive "old" 0.332
And I create a persistent partition 32.779
And I take note of which tps features are available 1.695
Then a Tails persistence partition exists on USB drive "old" 0.830
And I shutdown Tails and wait for the computer to power off 8.655
After features/support/hooks.rb:326 0.192
After features/support/hooks.rb:100 0.017
Tags: @product
2:53.734
Before features/support/hooks.rb:269 0.009
Given a computer 0.223
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.917
Then Tails is running from USB drive "old" 0.461
And all tps features are active 2.244
When I write some files expected to persist 1.801
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.261
And all persistence configuration files have safe access rights 0.518
And all persistent directories from the old Tails version have safe access rights 2.830
And I take note of which tps features are available 0.424
And I shutdown Tails and wait for the computer to power off 4.327
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.724
After features/support/hooks.rb:326 0.136
After features/support/hooks.rb:100 0.012
Tags: @product
2:42.427
Before features/support/hooks.rb:269 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 10.582
And I log in to a new session 19.027
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.483
And I plug USB drive "to_upgrade" 2.402
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.638
Then the running Tails is installed on USB drive "to_upgrade" 29.712
And I unplug USB drive "to_upgrade" 0.287
And I unplug USB drive "__internal" 0.292
After features/support/hooks.rb:326 3.737
After features/support/hooks.rb:100 0.000
Tags: @product
2:41.683
Before features/support/hooks.rb:269 0.011
Given a computer 0.304
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:30.727
Then all tps features from the old Tails version are active 1.864
And Tails is running from USB drive "to_upgrade" 0.375
And the boot device has safe access rights 4.162
And the expected persistent files created with the old Tails version are present in the filesystem 1.578
And all persistent directories from the old Tails version have safe access rights 2.670
After features/support/hooks.rb:326 0.654
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
7:12.116
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 25.403
And no SquashFS delta is installed 0.272
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.351
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.326
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.582
When the network is plugged 0.056
And Tor is ready 20.905
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.111
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.711
Given I shutdown Tails and wait for the computer to power off 11.131
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.776
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 7.096
And the file system changes introduced in version 6.2~testoverlayfs are present 0.349
And only the 6.2~testoverlayfs SquashFS delta is installed 0.093
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.375
# 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.354
When the network is plugged 0.069
And Tor is ready 19.742
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.527
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.328
Given I shutdown Tails and wait for the computer to power off 6.436
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.484
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 6.332
And the file system changes introduced in version 6.3~testoverlayfs are present 0.529
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.325
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.347
When the network is plugged 0.521
And Tor is ready 16.983
Then the Upgrader considers the system as up-to-date 0.324
# 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.826
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.254
After features/support/hooks.rb:326 0.939
After features/support/hooks.rb:100 0.030
Tags: @product @automatic_upgrade
43.310
Before features/support/hooks.rb:269 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 16.593
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.429
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the signing key used by the Upgrader is outdated 1.064
But a current signing key is available on our website 0.000
When the network is plugged 0.060
And Tor is ready 17.864
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.228
After features/support/hooks.rb:326 0.862
After features/support/hooks.rb:100 0.000