Project Number Date
test_Tails_ISO_stable 4560 09 Dec 2023, 12:15

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 17:3.808 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:40.700
Before features/support/hooks.rb:245 0.005
Given a computer 0.174
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 20.158
When I start Tails from USB drive "old" with network unplugged 1:15.168
Then the boot device has safe access rights 3.205
And Tails is running from USB drive "old" 0.292
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.063
And udev-watchdog is monitoring the correct device 0.254
And I unplug USB drive "old" 0.212
After features/support/hooks.rb:291 3.592
After features/support/hooks.rb:75 0.008
Tags: @product
2:6.529
Before features/support/hooks.rb:245 0.005
Given a computer 0.235
And I start Tails from USB drive "old" with network unplugged and I login 1:11.410
Then Tails is running from USB drive "old" 0.444
And I create a persistent partition 43.961
And I take note of which tps features are available 1.607
Then a Tails persistence partition exists on USB drive "old" 0.813
And I shutdown Tails and wait for the computer to power off 8.056
After features/support/hooks.rb:291 0.146
After features/support/hooks.rb:75 0.009
Tags: @product
2:17.158
Before features/support/hooks.rb:245 0.005
Given a computer 0.178
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:49.360
Then Tails is running from USB drive "old" 0.355
And all tps features are active 2.065
When I write some files expected to persist 1.766
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.223
And all persistence configuration files have safe access rights 0.569
And all persistent directories from the old Tails version have safe access rights 2.701
And I take note of which tps features are available 0.502
And I shutdown Tails and wait for the computer to power off 3.157
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 16.277
After features/support/hooks.rb:291 0.140
After features/support/hooks.rb:75 0.010
Tags: @product
2:34.668
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 10.277
And I log in to a new session 16.920
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.507
And I plug USB drive "to_upgrade" 2.578
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:48.176
Then the running Tails is installed on USB drive "to_upgrade" 14.792
And I unplug USB drive "to_upgrade" 0.222
And I unplug USB drive "__internal" 0.192
After features/support/hooks.rb:291 6.945
After features/support/hooks.rb:75 0.000
Tags: @product
2:1.364
Before features/support/hooks.rb:245 0.006
Given a computer 0.176
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:50.036
Then all tps features from the old Tails version are active 1.846
And Tails is running from USB drive "to_upgrade" 0.376
And the boot device has safe access rights 4.186
And the expected persistent files created with the old Tails version are present in the filesystem 1.871
And all persistent directories from the old Tails version have safe access rights 2.870
After features/support/hooks.rb:291 0.737
After features/support/hooks.rb:75 0.009
Tags: @product @automatic_upgrade
5:52.875
Before features/support/hooks.rb:245 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.961
And no SquashFS delta is installed 0.136
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.375
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.108
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.326
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.516
When the network is plugged 0.049
And Tor is ready 18.381
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 0.595
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.346
Given I shutdown Tails and wait for the computer to power off 7.101
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.821
Then Tails is running version 2.2~testoverlayfsng 0.105
And all tps features are active 2.134
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.392
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.092
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.275
# 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.300
When the network is plugged 0.038
And Tor is ready 13.386
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 4.092
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 9.719
Given I shutdown Tails and wait for the computer to power off 4.324
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:45.583
Then Tails is running version 2.3~testoverlayfsng 0.120
And all tps features are active 2.164
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.578
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.077
# 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.315
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.330
When the network is plugged 0.035
And Tor is ready 16.474
Then the Upgrader considers the system as up-to-date 0.286
# 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 26.723
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.602
After features/support/hooks.rb:291 0.850
After features/support/hooks.rb:75 0.023
Tags: @product @automatic_upgrade
30.511
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.141
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.312
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.058
And the signing key used by the Upgrader is outdated 0.549
But a current signing key is available on our website 0.000
When the network is plugged 0.033
And Tor is ready 15.692
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.723
After features/support/hooks.rb:291 1.161
After features/support/hooks.rb:75 0.000