Project Number Date
test_Tails_ISO_stable 4679 23 Feb 2024, 12:08

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:5.992 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:19.551
Before features/support/hooks.rb:245 0.006
Given a computer 0.152
And I create a 7200 MiB disk named "old" 0.029
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 19.068
When I start Tails from USB drive "old" with network unplugged 55.423
Then the boot device has safe access rights 2.948
And Tails is running from USB drive "old" 0.285
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.063
And udev-watchdog is monitoring the correct device 0.281
And I unplug USB drive "old" 0.189
After features/support/hooks.rb:291 3.431
After features/support/hooks.rb:75 0.024
Tags: @product
1:54.398
Before features/support/hooks.rb:245 0.005
Given a computer 0.146
And I start Tails from USB drive "old" with network unplugged and I login 1:1.492
Then Tails is running from USB drive "old" 0.372
And I create a persistent partition 43.190
And I take note of which tps features are available 1.249
Then a Tails persistence partition exists on USB drive "old" 0.864
And I shutdown Tails and wait for the computer to power off 7.083
After features/support/hooks.rb:291 0.143
After features/support/hooks.rb:75 0.009
Tags: @product
2:11.219
Before features/support/hooks.rb:245 0.005
Given a computer 0.145
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:45.705
Then Tails is running from USB drive "old" 0.332
And all tps features are active 1.859
When I write some files expected to persist 1.830
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.221
And all persistence configuration files have safe access rights 0.374
And all persistent directories from the old Tails version have safe access rights 2.724
And I take note of which tps features are available 0.330
And I shutdown Tails and wait for the computer to power off 3.058
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.637
After features/support/hooks.rb:291 0.102
After features/support/hooks.rb:75 0.009
Tags: @product
2:31.301
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 9.437
And I log in to a new session 15.041
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.130
And I plug USB drive "to_upgrade" 2.594
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:50.238
Then the running Tails is installed on USB drive "to_upgrade" 12.486
And I unplug USB drive "to_upgrade" 0.191
And I unplug USB drive "__internal" 0.180
After features/support/hooks.rb:291 1.911
After features/support/hooks.rb:75 0.000
Tags: @product
1:53.457
Before features/support/hooks.rb:245 0.006
Given a computer 0.187
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:43.665
Then all tps features from the old Tails version are active 1.635
And Tails is running from USB drive "to_upgrade" 0.286
And the boot device has safe access rights 3.566
And the expected persistent files created with the old Tails version are present in the filesystem 1.413
And all persistent directories from the old Tails version have safe access rights 2.702
After features/support/hooks.rb:291 0.708
After features/support/hooks.rb:75 0.009
Tags: @product @automatic_upgrade
5:50.549
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 12.658
And no SquashFS delta is installed 0.095
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.315
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.346
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.550
When the network is plugged 0.030
And Tor is ready 23.308
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 0.564
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.038
Given I shutdown Tails and wait for the computer to power off 5.092
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:42.049
Then Tails is running version 2.2~testoverlayfsng 0.085
And all tps features are active 1.719
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.362
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.066
# 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.288
When the network is plugged 0.026
And Tor is ready 12.963
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.571
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 9.898
Given I shutdown Tails and wait for the computer to power off 3.281
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:50.866
Then Tails is running version 2.3~testoverlayfsng 0.114
And all tps features are active 1.896
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.554
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.058
# 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.282
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.356
When the network is plugged 0.029
And Tor is ready 15.672
Then the Upgrader considers the system as up-to-date 10.685
# 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 23.941
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.447
After features/support/hooks.rb:291 0.828
After features/support/hooks.rb:75 0.018
Tags: @product @automatic_upgrade
25.513
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.359
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.310
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.061
And the signing key used by the Upgrader is outdated 0.611
But a current signing key is available on our website 0.000
When the network is plugged 0.024
And Tor is ready 12.488
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.656
After features/support/hooks.rb:291 0.721
After features/support/hooks.rb:75 0.000