Project Number Date
test_Tails_ISO_devel 3192 13 Dec 2023, 12:14

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 16:26.633 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:35.834
Before features/support/hooks.rb:245 0.005
Given a computer 0.189
And I create a 7200 MiB disk named "old" 0.053
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 20.940
When I start Tails from USB drive "old" with network unplugged 1:9.712
Then the boot device has safe access rights 2.954
And Tails is running from USB drive "old" 0.316
And there is no persistence partition on USB drive "old" 0.086
And process "udev-watchdog" is running 0.058
And udev-watchdog is monitoring the correct device 0.277
And I unplug USB drive "old" 0.186
After features/support/hooks.rb:291 3.470
After features/support/hooks.rb:75 0.010
Tags: @product
1:57.256
Before features/support/hooks.rb:245 0.006
Given a computer 0.206
And I start Tails from USB drive "old" with network unplugged and I login 1:0.888
Then Tails is running from USB drive "old" 0.517
And I create a persistent partition 45.280
And I take note of which tps features are available 1.412
Then a Tails persistence partition exists on USB drive "old" 0.888
And I shutdown Tails and wait for the computer to power off 8.062
After features/support/hooks.rb:291 0.199
After features/support/hooks.rb:75 0.008
Tags: @product
2:13.824
Before features/support/hooks.rb:245 0.005
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:45.457
Then Tails is running from USB drive "old" 0.408
And all tps features are active 2.342
When I write some files expected to persist 1.854
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.224
And all persistence configuration files have safe access rights 0.572
And all persistent directories from the old Tails version have safe access rights 2.903
And I take note of which tps features are available 0.477
And I shutdown Tails and wait for the computer to power off 3.062
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 16.319
After features/support/hooks.rb:291 0.115
After features/support/hooks.rb:75 0.010
Tags: @product
2:36.906
Before features/support/hooks.rb:245 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 10.615
And I log in to a new session 15.828
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.263
And I plug USB drive "to_upgrade" 2.521
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:52.240
Then the running Tails is installed on USB drive "to_upgrade" 14.028
And I unplug USB drive "to_upgrade" 0.237
And I unplug USB drive "__internal" 0.169
After features/support/hooks.rb:291 6.660
After features/support/hooks.rb:75 0.000
Tags: @product
2:1.909
Before features/support/hooks.rb:245 0.005
Given a computer 0.183
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:52.160
Then all tps features from the old Tails version are active 1.481
And Tails is running from USB drive "to_upgrade" 0.300
And the boot device has safe access rights 3.339
And the expected persistent files created with the old Tails version are present in the filesystem 1.560
And all persistent directories from the old Tails version have safe access rights 2.884
After features/support/hooks.rb:291 0.645
After features/support/hooks.rb:75 0.012
Tags: @product @automatic_upgrade
5:35.018
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.022
And no SquashFS delta is installed 0.099
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.292
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.080
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.412
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.519
When the network is plugged 0.065
And Tor is ready 14.884
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.652
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 11.040
Given I shutdown Tails and wait for the computer to power off 5.281
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:46.045
Then Tails is running version 2.2~testoverlayfsng 0.097
And all tps features are active 2.443
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.391
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.305
# 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.284
When the network is plugged 0.061
And Tor is ready 12.912
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.847
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.652
Given I shutdown Tails and wait for the computer to power off 3.333
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:45.532
Then Tails is running version 2.3~testoverlayfsng 0.115
And all tps features are active 2.172
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.608
And only the 2.3~testoverlayfsng 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.265
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.334
When the network is plugged 0.043
And Tor is ready 14.073
Then the Upgrader considers the system as up-to-date 0.299
# 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 27.305
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.373
After features/support/hooks.rb:291 0.790
After features/support/hooks.rb:75 0.019
Tags: @product @automatic_upgrade
25.883
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.709
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.445
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.065
And the signing key used by the Upgrader is outdated 0.550
But a current signing key is available on our website 0.000
When the network is plugged 0.043
And Tor is ready 13.425
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.642
After features/support/hooks.rb:291 0.701
After features/support/hooks.rb:75 0.000