Project Number Date
test_Tails_ISO_stable 4564 12 Dec 2023, 12:06

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:43.494 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:28.648
Before features/support/hooks.rb:245 0.005
Given a computer 0.202
And I create a 7200 MiB disk named "old" 0.057
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 20.406
When I start Tails from USB drive "old" with network unplugged 1:2.926
Then the boot device has safe access rights 3.134
And Tails is running from USB drive "old" 0.319
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.059
And udev-watchdog is monitoring the correct device 0.236
And I unplug USB drive "old" 0.186
After features/support/hooks.rb:291 3.758
After features/support/hooks.rb:75 0.008
Tags: @product
2:1.011
Before features/support/hooks.rb:245 0.004
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login 1:5.086
Then Tails is running from USB drive "old" 0.499
And I create a persistent partition 44.294
And I take note of which tps features are available 2.088
Then a Tails persistence partition exists on USB drive "old" 0.749
And I shutdown Tails and wait for the computer to power off 8.102
After features/support/hooks.rb:291 0.142
After features/support/hooks.rb:75 0.008
Tags: @product
2:19.064
Before features/support/hooks.rb:245 0.007
Given a computer 0.217
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:52.359
Then Tails is running from USB drive "old" 0.363
And all tps features are active 1.955
When I write some files expected to persist 1.811
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.252
And all persistence configuration files have safe access rights 0.585
And all persistent directories from the old Tails version have safe access rights 2.784
And I take note of which tps features are available 0.600
And I shutdown Tails and wait for the computer to power off 3.071
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.061
After features/support/hooks.rb:291 0.135
After features/support/hooks.rb:75 0.008
Tags: @product
2:30.668
Before features/support/hooks.rb:245 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.313
And I log in to a new session 15.149
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.277
And I plug USB drive "to_upgrade" 2.477
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:47.223
Then the running Tails is installed on USB drive "to_upgrade" 14.840
And I unplug USB drive "to_upgrade" 0.211
And I unplug USB drive "__internal" 0.174
After features/support/hooks.rb:291 6.850
After features/support/hooks.rb:75 0.000
Tags: @product
2:6.009
Before features/support/hooks.rb:245 0.006
Given a computer 0.178
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:55.266
Then all tps features from the old Tails version are active 2.023
And Tails is running from USB drive "to_upgrade" 0.366
And the boot device has safe access rights 3.582
And the expected persistent files created with the old Tails version are present in the filesystem 1.791
And all persistent directories from the old Tails version have safe access rights 2.800
After features/support/hooks.rb:291 0.646
After features/support/hooks.rb:75 0.011
Tags: @product @automatic_upgrade
5:50.574
Before features/support/hooks.rb:245 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.403
And no SquashFS delta is installed 0.102
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.457
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.480
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.549
When the network is plugged 0.034
And Tor is ready 18.038
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.612
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.708
Given I shutdown Tails and wait for the computer to power off 6.244
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.207
Then Tails is running version 2.2~testoverlayfsng 0.119
And all tps features are active 2.207
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.384
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.309
# 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.364
When the network is plugged 0.052
And Tor is ready 15.570
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.704
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 9.399
Given I shutdown Tails and wait for the computer to power off 4.273
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.759
Then Tails is running version 2.3~testoverlayfsng 0.095
And all tps features are active 2.036
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.556
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.061
# 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.289
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.292
When the network is plugged 0.041
And Tor is ready 15.475
Then the Upgrader considers the system as up-to-date 0.281
# 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 24.868
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.407
After features/support/hooks.rb:291 0.790
After features/support/hooks.rb:75 0.020
Tags: @product @automatic_upgrade
27.517
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 9.800
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.334
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.061
And the signing key used by the Upgrader is outdated 0.847
But a current signing key is available on our website 0.000
When the network is plugged 0.040
And Tor is ready 14.642
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.791
After features/support/hooks.rb:291 0.674
After features/support/hooks.rb:75 0.000