Project Number Date
test_Tails_ISO_stable 4586 22 Dec 2023, 14:24

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:51.308 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:33.189
Before features/support/hooks.rb:245 0.006
Given a computer 0.185
And I create a 7200 MiB disk named "old" 0.057
And I plug USB drive "old" 1.059
And I write an old version of the Tails USB image to disk "old" 19.899
When I start Tails from USB drive "old" with network unplugged 1:7.756
Then the boot device has safe access rights 3.307
And Tails is running from USB drive "old" 0.340
And there is no persistence partition on USB drive "old" 0.054
And process "udev-watchdog" is running 0.061
And udev-watchdog is monitoring the correct device 0.246
And I unplug USB drive "old" 0.219
After features/support/hooks.rb:291 3.583
After features/support/hooks.rb:75 0.025
Tags: @product
1:59.574
Before features/support/hooks.rb:245 0.007
Given a computer 0.193
And I start Tails from USB drive "old" with network unplugged and I login 1:5.968
Then Tails is running from USB drive "old" 0.454
And I create a persistent partition 42.494
And I take note of which tps features are available 1.470
Then a Tails persistence partition exists on USB drive "old" 0.869
And I shutdown Tails and wait for the computer to power off 8.124
After features/support/hooks.rb:291 0.108
After features/support/hooks.rb:75 0.009
Tags: @product
2:25.470
Before features/support/hooks.rb:245 0.004
Given a computer 0.173
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:58.045
Then Tails is running from USB drive "old" 0.368
And all tps features are active 2.229
When I write some files expected to persist 2.126
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.251
And all persistence configuration files have safe access rights 0.612
And all persistent directories from the old Tails version have safe access rights 3.033
And I take note of which tps features are available 0.514
And I shutdown Tails and wait for the computer to power off 3.078
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.035
After features/support/hooks.rb:291 0.138
After features/support/hooks.rb:75 0.010
Tags: @product
2:38.324
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 10.533
And I log in to a new session 19.575
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.116
And I plug USB drive "to_upgrade" 2.524
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:50.113
Then the running Tails is installed on USB drive "to_upgrade" 14.091
And I unplug USB drive "to_upgrade" 0.201
And I unplug USB drive "__internal" 0.168
After features/support/hooks.rb:291 3.564
After features/support/hooks.rb:75 0.000
Tags: @product
1:56.809
Before features/support/hooks.rb:245 0.006
Given a computer 0.190
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:47.012
Then all tps features from the old Tails version are active 1.615
And Tails is running from USB drive "to_upgrade" 0.376
And the boot device has safe access rights 3.454
And the expected persistent files created with the old Tails version are present in the filesystem 1.478
And all persistent directories from the old Tails version have safe access rights 2.680
After features/support/hooks.rb:291 0.691
After features/support/hooks.rb:75 0.009
Tags: @product @automatic_upgrade
5:50.824
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 11.584
And no SquashFS delta is installed 0.163
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.327
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.053
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.349
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.549
When the network is plugged 0.044
And Tor is ready 17.551
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.961
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.690
Given I shutdown Tails and wait for the computer to power off 6.262
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.226
Then Tails is running version 2.2~testoverlayfsng 0.131
And all tps features are active 2.510
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.428
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.300
# 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.320
When the network is plugged 0.043
And Tor is ready 17.099
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.639
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.041
Given I shutdown Tails and wait for the computer to power off 3.298
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.374
Then Tails is running version 2.3~testoverlayfsng 0.099
And all tps features are active 2.180
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.562
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.079
# 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.272
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.291
When the network is plugged 0.038
And Tor is ready 18.104
Then the Upgrader considers the system as up-to-date 0.508
# 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 25.886
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.786
After features/support/hooks.rb:291 1.012
After features/support/hooks.rb:75 0.020
Tags: @product @automatic_upgrade
27.115
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.380
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.309
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 1.943
But a current signing key is available on our website 0.000
When the network is plugged 0.041
And Tor is ready 13.827
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.554
After features/support/hooks.rb:291 0.647
After features/support/hooks.rb:75 0.000