Project Number Date
test_Tails_ISO_stable 4587 23 Dec 2023, 12:02

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:12.489 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:22.590
Before features/support/hooks.rb:245 0.007
Given a computer 0.166
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 22.039
When I start Tails from USB drive "old" with network unplugged 55.440
Then the boot device has safe access rights 2.892
And Tails is running from USB drive "old" 0.345
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.062
And udev-watchdog is monitoring the correct device 0.279
And I unplug USB drive "old" 0.203
After features/support/hooks.rb:291 3.594
After features/support/hooks.rb:75 0.010
Tags: @product
2:0.020
Before features/support/hooks.rb:245 0.006
Given a computer 0.206
And I start Tails from USB drive "old" with network unplugged and I login 1:4.012
Then Tails is running from USB drive "old" 0.363
And I create a persistent partition 44.905
And I take note of which tps features are available 1.569
Then a Tails persistence partition exists on USB drive "old" 0.885
And I shutdown Tails and wait for the computer to power off 8.077
After features/support/hooks.rb:291 0.117
After features/support/hooks.rb:75 0.008
Tags: @product
2:13.853
Before features/support/hooks.rb:245 0.004
Given a computer 0.180
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:46.914
Then Tails is running from USB drive "old" 0.363
And all tps features are active 2.214
When I write some files expected to persist 1.847
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.214
And all persistence configuration files have safe access rights 0.653
And all persistent directories from the old Tails version have safe access rights 2.678
And I take note of which tps features are available 0.686
And I shutdown Tails and wait for the computer to power off 3.062
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.038
After features/support/hooks.rb:291 0.145
After features/support/hooks.rb:75 0.009
Tags: @product
2:31.106
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 10.042
And I log in to a new session 14.345
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.116
And I plug USB drive "to_upgrade" 2.412
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:48.422
Then the running Tails is installed on USB drive "to_upgrade" 14.401
And I unplug USB drive "to_upgrade" 0.189
And I unplug USB drive "__internal" 0.177
After features/support/hooks.rb:291 6.679
After features/support/hooks.rb:75 0.000
Tags: @product
1:57.429
Before features/support/hooks.rb:245 0.009
Given a computer 0.241
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:46.653
Then all tps features from the old Tails version are active 1.627
And Tails is running from USB drive "to_upgrade" 0.349
And the boot device has safe access rights 3.948
And the expected persistent files created with the old Tails version are present in the filesystem 1.656
And all persistent directories from the old Tails version have safe access rights 2.953
After features/support/hooks.rb:291 0.698
After features/support/hooks.rb:75 0.009
Tags: @product @automatic_upgrade
5:37.433
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.105
And no SquashFS delta is installed 0.144
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.379
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.077
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.374
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.685
When the network is plugged 0.043
And Tor is ready 14.864
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.662
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.477
Given I shutdown Tails and wait for the computer to power off 5.326
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:46.605
Then Tails is running version 2.2~testoverlayfsng 0.103
And all tps features are active 2.288
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.418
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.273
# 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.264
When the network is plugged 0.059
And Tor is ready 15.019
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.739
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 10.032
Given I shutdown Tails and wait for the computer to power off 3.360
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:47.560
Then Tails is running version 2.3~testoverlayfsng 0.196
And all tps features are active 2.067
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.582
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.070
# 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.287
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.340
When the network is plugged 0.204
And Tor is ready 14.429
Then the Upgrader considers the system as up-to-date 0.228
# 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.787
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.301
After features/support/hooks.rb:291 0.722
After features/support/hooks.rb:75 0.019
Tags: @product @automatic_upgrade
30.055
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.396
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.339
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.082
And the signing key used by the Upgrader is outdated 0.816
But a current signing key is available on our website 0.000
When the network is plugged 0.042
And Tor is ready 17.711
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.665
After features/support/hooks.rb:291 1.000
After features/support/hooks.rb:75 0.000