Project Number Date
test_Tails_ISO_devel 3198 18 Dec 2023, 12:26

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:2.460 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:17.685
Before features/support/hooks.rb:245 0.006
Given a computer 0.173
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.066
And I write an old version of the Tails USB image to disk "old" 18.199
When I start Tails from USB drive "old" with network unplugged 54.246
Then the boot device has safe access rights 3.023
And Tails is running from USB drive "old" 0.332
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.063
And udev-watchdog is monitoring the correct device 0.288
And I unplug USB drive "old" 0.179
After features/support/hooks.rb:291 3.457
After features/support/hooks.rb:75 0.010
Tags: @product
1:56.701
Before features/support/hooks.rb:245 0.006
Given a computer 0.180
And I start Tails from USB drive "old" with network unplugged and I login 1:4.063
Then Tails is running from USB drive "old" 0.371
And I create a persistent partition 42.892
And I take note of which tps features are available 1.312
Then a Tails persistence partition exists on USB drive "old" 0.810
And I shutdown Tails and wait for the computer to power off 7.069
After features/support/hooks.rb:291 0.106
After features/support/hooks.rb:75 0.010
Tags: @product
2:10.700
Before features/support/hooks.rb:245 0.008
Given a computer 0.208
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:43.270
Then Tails is running from USB drive "old" 0.388
And all tps features are active 2.310
When I write some files expected to persist 1.748
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.235
And all persistence configuration files have safe access rights 0.590
And all persistent directories from the old Tails version have safe access rights 2.651
And I take note of which tps features are available 0.449
And I shutdown Tails and wait for the computer to power off 3.066
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.780
After features/support/hooks.rb:291 0.098
After features/support/hooks.rb:75 0.010
Tags: @product
2:31.182
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.913
And I log in to a new session 16.017
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.067
And I plug USB drive "to_upgrade" 2.573
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:47.845
Then the running Tails is installed on USB drive "to_upgrade" 13.318
And I unplug USB drive "to_upgrade" 0.226
And I unplug USB drive "__internal" 0.219
After features/support/hooks.rb:291 6.336
After features/support/hooks.rb:75 0.000
Tags: @product
1:52.580
Before features/support/hooks.rb:245 0.009
Given a computer 0.206
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:42.241
Then all tps features from the old Tails version are active 1.778
And Tails is running from USB drive "to_upgrade" 0.372
And the boot device has safe access rights 3.596
And the expected persistent files created with the old Tails version are present in the filesystem 1.486
And all persistent directories from the old Tails version have safe access rights 2.898
After features/support/hooks.rb:291 0.622
After features/support/hooks.rb:75 0.014
Tags: @product @automatic_upgrade
5:46.609
Before features/support/hooks.rb:245 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.621
And no SquashFS delta is installed 0.130
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.485
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.430
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.541
When the network is plugged 0.067
And Tor is ready 15.932
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.863
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.722
Given I shutdown Tails and wait for the computer to power off 7.346
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:45.622
Then Tails is running version 2.2~testoverlayfsng 0.122
And all tps features are active 2.402
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.854
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.094
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.322
# 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.350
When the network is plugged 0.036
And Tor is ready 14.313
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.632
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 9.177
Given I shutdown Tails and wait for the computer to power off 3.397
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:50.172
Then Tails is running version 2.3~testoverlayfsng 0.105
And all tps features are active 2.245
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.802
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.088
# 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.332
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.398
When the network is plugged 0.057
And Tor is ready 15.814
Then the Upgrader considers the system as up-to-date 0.260
# 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 28.651
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.129
After features/support/hooks.rb:291 0.778
After features/support/hooks.rb:75 0.016
Tags: @product @automatic_upgrade
27.000
Before features/support/hooks.rb:245 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.838
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.349
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.117
And the signing key used by the Upgrader is outdated 0.617
But a current signing key is available on our website 0.000
When the network is plugged 0.053
And Tor is ready 13.202
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.822
After features/support/hooks.rb:291 0.774
After features/support/hooks.rb:75 0.000