Project Number Date
test_Tails_ISO_stable 4568 13 Dec 2023, 16:02

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 15:46.437 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
1:22.162
Before features/support/hooks.rb:245 0.005
Given a computer 0.147
And I create a 7200 MiB disk named "old" 0.030
And I plug USB drive "old" 1.043
And I write an old version of the Tails USB image to disk "old" 20.989
When I start Tails from USB drive "old" with network unplugged 56.045
Then the boot device has safe access rights 3.043
And Tails is running from USB drive "old" 0.297
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.059
And udev-watchdog is monitoring the correct device 0.260
And I unplug USB drive "old" 0.177
After features/support/hooks.rb:291 3.505
After features/support/hooks.rb:75 0.010
Tags: @product
1:52.940
Before features/support/hooks.rb:245 0.006
Given a computer 0.137
And I start Tails from USB drive "old" with network unplugged and I login 1:0.739
Then Tails is running from USB drive "old" 0.375
And I create a persistent partition 42.684
And I take note of which tps features are available 1.163
Then a Tails persistence partition exists on USB drive "old" 0.765
And I shutdown Tails and wait for the computer to power off 7.075
After features/support/hooks.rb:291 0.136
After features/support/hooks.rb:75 0.011
Tags: @product
2:17.691
Before features/support/hooks.rb:245 0.007
Given a computer 0.139
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:50.483
Then Tails is running from USB drive "old" 0.358
And all tps features are active 1.854
When I write some files expected to persist 1.852
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.266
And all persistence configuration files have safe access rights 0.624
And all persistent directories from the old Tails version have safe access rights 2.748
And I take note of which tps features are available 0.339
And I shutdown Tails and wait for the computer to power off 3.077
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.946
After features/support/hooks.rb:291 0.110
After features/support/hooks.rb:75 0.010
Tags: @product
2:31.130
Before features/support/hooks.rb:245 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 9.360
And I log in to a new session 14.713
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.180
And I plug USB drive "to_upgrade" 2.541
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:49.979
Then the running Tails is installed on USB drive "to_upgrade" 12.965
And I unplug USB drive "to_upgrade" 0.202
And I unplug USB drive "__internal" 0.185
After features/support/hooks.rb:291 3.780
After features/support/hooks.rb:75 0.000
Tags: @product
1:50.644
Before features/support/hooks.rb:245 0.007
Given a computer 0.150
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:41.093
Then all tps features from the old Tails version are active 1.277
And Tails is running from USB drive "to_upgrade" 0.325
And the boot device has safe access rights 3.287
And the expected persistent files created with the old Tails version are present in the filesystem 1.666
And all persistent directories from the old Tails version have safe access rights 2.843
After features/support/hooks.rb:291 0.895
After features/support/hooks.rb:75 0.009
Tags: @product @automatic_upgrade
5:28.861
Before features/support/hooks.rb:245 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.655
And no SquashFS delta is installed 0.084
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.373
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.065
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.408
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.583
When the network is plugged 0.032
And Tor is ready 14.818
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.690
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.105
Given I shutdown Tails and wait for the computer to power off 5.218
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:42.990
Then Tails is running version 2.2~testoverlayfsng 0.095
And all tps features are active 1.722
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.342
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.061
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.284
# We'll really install Tails_amd64_2.0~testoverlayfsng_to_2.3~testoverlayfsng.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 2.1~testoverlayfsng was initially installed 0.313
When the network is plugged 0.031
And Tor is ready 14.189
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.654
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.473
Given I shutdown Tails and wait for the computer to power off 3.066
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.701
Then Tails is running version 2.3~testoverlayfsng 0.096
And all tps features are active 1.634
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.526
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.064
# 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.277
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.291
When the network is plugged 0.025
And Tor is ready 13.290
Then the Upgrader considers the system as up-to-date 0.303
# 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 25.162
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.226
After features/support/hooks.rb:291 0.788
After features/support/hooks.rb:75 0.020
Tags: @product @automatic_upgrade
23.007
Before features/support/hooks.rb:245 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.141
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.365
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.048
And the signing key used by the Upgrader is outdated 0.443
But a current signing key is available on our website 0.000
When the network is plugged 0.026
And Tor is ready 12.440
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 0.541
After features/support/hooks.rb:291 0.681
After features/support/hooks.rb:75 0.000