Project Number Date
test_Tails_ISO_stable 4556 07 Dec 2023, 18:59

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:31.192 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:42.352
Before features/support/hooks.rb:245 0.005
Given a computer 0.170
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 22.220
When I start Tails from USB drive "old" with network unplugged 1:14.398
Then the boot device has safe access rights 3.451
And Tails is running from USB drive "old" 0.343
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.068
And udev-watchdog is monitoring the correct device 0.328
And I unplug USB drive "old" 0.201
After features/support/hooks.rb:291 3.699
After features/support/hooks.rb:75 0.009
Tags: @product
2:4.209
Before features/support/hooks.rb:245 0.005
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login 1:6.451
Then Tails is running from USB drive "old" 0.600
And I create a persistent partition 44.903
And I take note of which tps features are available 2.612
Then a Tails persistence partition exists on USB drive "old" 1.201
And I shutdown Tails and wait for the computer to power off 8.254
After features/support/hooks.rb:291 0.149
After features/support/hooks.rb:75 0.011
Tags: @product
2:29.834
Before features/support/hooks.rb:245 0.010
Given a computer 0.222
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:0.670
Then Tails is running from USB drive "old" 0.364
And all tps features are active 2.217
When I write some files expected to persist 2.175
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.239
And all persistence configuration files have safe access rights 0.664
And all persistent directories from the old Tails version have safe access rights 2.881
And I take note of which tps features are available 0.558
And I shutdown Tails and wait for the computer to power off 3.073
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 16.765
After features/support/hooks.rb:291 0.139
After features/support/hooks.rb:75 0.009
Tags: @product
2:33.995
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.938
And I log in to a new session 17.431
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.257
And I plug USB drive "to_upgrade" 2.478
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:49.427
Then the running Tails is installed on USB drive "to_upgrade" 13.064
And I unplug USB drive "to_upgrade" 0.200
And I unplug USB drive "__internal" 0.198
After features/support/hooks.rb:291 1.488
After features/support/hooks.rb:75 0.000
Tags: @product
2:5.381
Before features/support/hooks.rb:245 0.007
Given a computer 0.202
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:53.839
Then all tps features from the old Tails version are active 1.876
And Tails is running from USB drive "to_upgrade" 0.436
And the boot device has safe access rights 4.249
And the expected persistent files created with the old Tails version are present in the filesystem 1.959
And all persistent directories from the old Tails version have safe access rights 2.816
After features/support/hooks.rb:291 0.737
After features/support/hooks.rb:75 0.013
Tags: @product @automatic_upgrade
6:5.639
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.718
And no SquashFS delta is installed 0.129
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.387
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.079
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.455
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.644
When the network is plugged 0.046
And Tor is ready 16.696
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.761
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.306
Given I shutdown Tails and wait for the computer to power off 5.356
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.319
Then Tails is running version 2.2~testoverlayfsng 0.123
And all tps features are active 2.690
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.474
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.082
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.267
# 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.404
When the network is plugged 0.046
And Tor is ready 13.747
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.979
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 11.155
Given I shutdown Tails and wait for the computer to power off 4.735
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.103
Then Tails is running version 2.3~testoverlayfsng 0.177
And all tps features are active 2.046
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.617
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.286
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.318
When the network is plugged 0.040
And Tor is ready 14.669
Then the Upgrader considers the system as up-to-date 0.324
# 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.953
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 2.410
After features/support/hooks.rb:291 1.036
After features/support/hooks.rb:75 0.023
Tags: @product @automatic_upgrade
29.780
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.756
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.399
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.090
And the signing key used by the Upgrader is outdated 0.786
But a current signing key is available on our website 0.000
When the network is plugged 0.753
And Tor is ready 15.322
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.671
After features/support/hooks.rb:291 1.145
After features/support/hooks.rb:75 0.000