Project Number Date
test_Tails_ISO_stable 4578 20 Dec 2023, 12:14

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:30.451 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.331
Before features/support/hooks.rb:245 0.007
Given a computer 0.186
And I create a 7200 MiB disk named "old" 0.058
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 21.548
When I start Tails from USB drive "old" with network unplugged 1:14.642
Then the boot device has safe access rights 3.731
And Tails is running from USB drive "old" 0.430
And there is no persistence partition on USB drive "old" 0.082
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.305
And I unplug USB drive "old" 0.190
After features/support/hooks.rb:291 3.716
After features/support/hooks.rb:75 0.011
Tags: @product
2:0.989
Before features/support/hooks.rb:245 0.007
Given a computer 0.216
And I start Tails from USB drive "old" with network unplugged and I login 1:6.725
Then Tails is running from USB drive "old" 0.380
And I create a persistent partition 43.658
And I take note of which tps features are available 1.994
Then a Tails persistence partition exists on USB drive "old" 0.939
And I shutdown Tails and wait for the computer to power off 7.073
After features/support/hooks.rb:291 0.112
After features/support/hooks.rb:75 0.009
Tags: @product
2:22.870
Before features/support/hooks.rb:245 0.005
Given a computer 0.207
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:55.682
Then Tails is running from USB drive "old" 0.392
And all tps features are active 2.084
When I write some files expected to persist 1.875
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.228
And all persistence configuration files have safe access rights 0.616
And all persistent directories from the old Tails version have safe access rights 2.974
And I take note of which tps features are available 0.475
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" 15.273
After features/support/hooks.rb:291 0.151
After features/support/hooks.rb:75 0.010
Tags: @product
2:35.835
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.875
And I log in to a new session 17.798
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.370
And I plug USB drive "to_upgrade" 2.482
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:49.495
Then the running Tails is installed on USB drive "to_upgrade" 13.373
And I unplug USB drive "to_upgrade" 0.226
And I unplug USB drive "__internal" 0.212
After features/support/hooks.rb:291 3.752
After features/support/hooks.rb:75 0.000
Tags: @product
2:12.562
Before features/support/hooks.rb:245 0.005
Given a computer 0.195
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:0.461
Then all tps features from the old Tails version are active 2.185
And Tails is running from USB drive "to_upgrade" 0.418
And the boot device has safe access rights 4.388
And the expected persistent files created with the old Tails version are present in the filesystem 1.767
And all persistent directories from the old Tails version have safe access rights 3.144
After features/support/hooks.rb:291 0.825
After features/support/hooks.rb:75 0.013
Tags: @product @automatic_upgrade
6:5.988
Before features/support/hooks.rb:245 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.551
And no SquashFS delta is installed 0.104
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.422
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.094
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.587
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.574
When the network is plugged 0.036
And Tor is ready 16.798
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.780
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 10.653
Given I shutdown Tails and wait for the computer to power off 6.372
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.061
Then Tails is running version 2.2~testoverlayfsng 0.115
And all tps features are active 2.605
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.442
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.085
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.347
# 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.376
When the network is plugged 0.045
And Tor is ready 15.233
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 4.110
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 9.119
Given I shutdown Tails and wait for the computer to power off 4.324
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.976
Then Tails is running version 2.3~testoverlayfsng 0.111
And all tps features are active 2.425
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.642
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.096
# 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.279
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.314
When the network is plugged 0.044
And Tor is ready 17.804
Then the Upgrader considers the system as up-to-date 0.247
# 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.717
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.484
After features/support/hooks.rb:291 0.830
After features/support/hooks.rb:75 0.021
Tags: @product @automatic_upgrade
29.874
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.309
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.044
And the signing key used by the Upgrader is outdated 0.501
But a current signing key is available on our website 0.000
When the network is plugged 0.052
And Tor is ready 14.782
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.797
After features/support/hooks.rb:291 0.926
After features/support/hooks.rb:75 0.000