Project Number Date
test_Tails_ISO_stable 4674 19 Feb 2024, 14:57

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.296 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.178
Before features/support/hooks.rb:245 0.007
Given a computer 0.212
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 23.206
When I start Tails from USB drive "old" with network unplugged 59.583
Then the boot device has safe access rights 3.177
And Tails is running from USB drive "old" 0.324
And there is no persistence partition on USB drive "old" 0.060
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.257
And I unplug USB drive "old" 0.197
After features/support/hooks.rb:291 3.733
After features/support/hooks.rb:75 0.013
Tags: @product
2:0.796
Before features/support/hooks.rb:245 0.007
Given a computer 0.420
And I start Tails from USB drive "old" with network unplugged and I login 1:7.901
Then Tails is running from USB drive "old" 0.441
And I create a persistent partition 42.708
And I take note of which tps features are available 1.467
Then a Tails persistence partition exists on USB drive "old" 0.796
And I shutdown Tails and wait for the computer to power off 7.060
After features/support/hooks.rb:291 0.166
After features/support/hooks.rb:75 0.011
Tags: @product
2:21.545
Before features/support/hooks.rb:245 0.006
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:52.576
Then Tails is running from USB drive "old" 0.330
And all tps features are active 2.057
When I write some files expected to persist 1.876
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.264
And all persistence configuration files have safe access rights 0.541
And all persistent directories from the old Tails version have safe access rights 3.265
And I take note of which tps features are available 0.523
And I shutdown Tails and wait for the computer to power off 3.076
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 16.836
After features/support/hooks.rb:291 0.138
After features/support/hooks.rb:75 0.008
Tags: @product
2:36.459
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 11.664
And I log in to a new session 16.205
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.199
And I plug USB drive "to_upgrade" 2.455
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:51.163
Then the running Tails is installed on USB drive "to_upgrade" 13.363
And I unplug USB drive "to_upgrade" 0.202
And I unplug USB drive "__internal" 0.204
After features/support/hooks.rb:291 7.175
After features/support/hooks.rb:75 0.000
Tags: @product
2:9.094
Before features/support/hooks.rb:245 0.013
Given a computer 0.192
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:58.091
Then all tps features from the old Tails version are active 1.751
And Tails is running from USB drive "to_upgrade" 0.421
And the boot device has safe access rights 4.219
And the expected persistent files created with the old Tails version are present in the filesystem 1.617
And all persistent directories from the old Tails version have safe access rights 2.800
After features/support/hooks.rb:291 0.696
After features/support/hooks.rb:75 0.008
Tags: @product @automatic_upgrade
6:0.994
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.294
And no SquashFS delta is installed 0.113
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.266
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.074
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.390
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.507
When the network is plugged 0.048
And Tor is ready 18.179
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.705
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.147
Given I shutdown Tails and wait for the computer to power off 6.255
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.359
Then Tails is running version 2.2~testoverlayfsng 0.110
And all tps features are active 2.437
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.528
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.097
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.346
# 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.316
When the network is plugged 0.033
And Tor is ready 15.471
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.938
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.947
Given I shutdown Tails and wait for the computer to power off 5.675
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.575
Then Tails is running version 2.3~testoverlayfsng 0.119
And all tps features are active 2.141
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.639
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.298
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.320
When the network is plugged 0.045
And Tor is ready 15.471
Then the Upgrader considers the system as up-to-date 0.275
# 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 26.014
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.773
After features/support/hooks.rb:291 0.772
After features/support/hooks.rb:75 0.018
Tags: @product @automatic_upgrade
28.227
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 9.033
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.363
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.619
But a current signing key is available on our website 0.000
When the network is plugged 0.044
And Tor is ready 14.201
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.907
After features/support/hooks.rb:291 0.732
After features/support/hooks.rb:75 0.000