Project Number Date
test_Tails_ISO_stable 4572 18 Dec 2023, 12:10

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:5.028 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:31.807
Before features/support/hooks.rb:245 0.007
Given a computer 0.226
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.045
And I write an old version of the Tails USB image to disk "old" 20.003
When I start Tails from USB drive "old" with network unplugged 1:6.369
Then the boot device has safe access rights 3.218
And Tails is running from USB drive "old" 0.309
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.280
And I unplug USB drive "old" 0.186
After features/support/hooks.rb:291 3.497
After features/support/hooks.rb:75 0.009
Tags: @product
1:57.944
Before features/support/hooks.rb:245 0.006
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login 1:4.556
Then Tails is running from USB drive "old" 0.446
And I create a persistent partition 42.504
And I take note of which tps features are available 1.336
Then a Tails persistence partition exists on USB drive "old" 0.828
And I shutdown Tails and wait for the computer to power off 8.067
After features/support/hooks.rb:291 0.142
After features/support/hooks.rb:75 0.010
Tags: @product
2:17.451
Before features/support/hooks.rb:245 0.005
Given a computer 0.184
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:50.943
Then Tails is running from USB drive "old" 0.343
And all tps features are active 2.165
When I write some files expected to persist 1.946
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.247
And all persistence configuration files have safe access rights 0.625
And all persistent directories from the old Tails version have safe access rights 2.543
And I take note of which tps features are available 0.510
And I shutdown Tails and wait for the computer to power off 3.063
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.877
After features/support/hooks.rb:291 0.150
After features/support/hooks.rb:75 0.008
Tags: @product
2:32.584
Before features/support/hooks.rb:245 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.936
And I log in to a new session 18.140
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.188
And I plug USB drive "to_upgrade" 2.673
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:48.293
Then the running Tails is installed on USB drive "to_upgrade" 11.974
And I unplug USB drive "to_upgrade" 0.203
And I unplug USB drive "__internal" 0.174
After features/support/hooks.rb:291 5.335
After features/support/hooks.rb:75 0.000
Tags: @product
1:58.377
Before features/support/hooks.rb:245 0.006
Given a computer 0.179
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:47.879
Then all tps features from the old Tails version are active 1.750
And Tails is running from USB drive "to_upgrade" 0.391
And the boot device has safe access rights 3.729
And the expected persistent files created with the old Tails version are present in the filesystem 1.683
And all persistent directories from the old Tails version have safe access rights 2.763
After features/support/hooks.rb:291 0.629
After features/support/hooks.rb:75 0.009
Tags: @product @automatic_upgrade
6:18.634
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 10.293
And no SquashFS delta is installed 0.108
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.362
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.196
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.497
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.543
When the network is plugged 0.033
And Tor is ready 45.598
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 0.641
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 10.259
Given I shutdown Tails and wait for the computer to power off 8.358
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.195
Then Tails is running version 2.2~testoverlayfsng 0.111
And all tps features are active 2.393
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.457
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.078
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.341
# 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.318
When the network is plugged 0.051
And Tor is ready 15.991
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 3.159
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 9.326
Given I shutdown Tails and wait for the computer to power off 4.318
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:44.859
Then Tails is running version 2.3~testoverlayfsng 0.138
And all tps features are active 2.240
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.777
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.083
# 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.337
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.363
When the network is plugged 0.059
And Tor is ready 14.275
Then the Upgrader considers the system as up-to-date 0.288
# 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.315
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.257
After features/support/hooks.rb:291 0.867
After features/support/hooks.rb:75 0.020
Tags: @product @automatic_upgrade
28.228
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 10.247
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.303
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.185
And the signing key used by the Upgrader is outdated 0.658
But a current signing key is available on our website 0.000
When the network is plugged 0.045
And Tor is ready 14.950
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.837
After features/support/hooks.rb:291 0.748
After features/support/hooks.rb:75 0.000