Project Number Date
test_Tails_ISO_stable 4538 28 Nov 2023, 00:16

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:38.975 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:30.652
Before features/support/hooks.rb:245 0.008
Given a computer 0.332
And I create a 7200 MiB disk named "old" 0.113
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 19.892
When I start Tails from USB drive "old" with network unplugged 1:5.381
Then the boot device has safe access rights 2.992
And Tails is running from USB drive "old" 0.321
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.058
And udev-watchdog is monitoring the correct device 0.247
And I unplug USB drive "old" 0.194
After features/support/hooks.rb:291 3.519
After features/support/hooks.rb:75 0.012
Tags: @product
1:58.877
Before features/support/hooks.rb:245 0.008
Given a computer 0.215
And I start Tails from USB drive "old" with network unplugged and I login 1:5.908
Then Tails is running from USB drive "old" 0.372
And I create a persistent partition 43.128
And I take note of which tps features are available 1.361
Then a Tails persistence partition exists on USB drive "old" 0.819
And I shutdown Tails and wait for the computer to power off 7.072
After features/support/hooks.rb:291 0.132
After features/support/hooks.rb:75 0.011
Tags: @product
2:19.614
Before features/support/hooks.rb:245 0.008
Given a computer 0.200
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:53.026
Then Tails is running from USB drive "old" 0.298
And all tps features are active 2.207
When I write some files expected to persist 1.891
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.277
And all persistence configuration files have safe access rights 0.649
And all persistent directories from the old Tails version have safe access rights 2.489
And I take note of which tps features are available 0.496
And I shutdown Tails and wait for the computer to power off 3.077
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.000
After features/support/hooks.rb:291 0.112
After features/support/hooks.rb:75 0.010
Tags: @product
2:34.501
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 11.933
And I log in to a new session 16.902
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.403
And I plug USB drive "to_upgrade" 2.458
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:48.444
Then the running Tails is installed on USB drive "to_upgrade" 12.980
And I unplug USB drive "to_upgrade" 0.204
And I unplug USB drive "__internal" 0.173
After features/support/hooks.rb:291 8.990
After features/support/hooks.rb:75 0.000
Tags: @product
2:2.820
Before features/support/hooks.rb:245 0.009
Given a computer 0.246
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:52.406
Then all tps features from the old Tails version are active 1.722
And Tails is running from USB drive "to_upgrade" 0.314
And the boot device has safe access rights 3.578
And the expected persistent files created with the old Tails version are present in the filesystem 1.673
And all persistent directories from the old Tails version have safe access rights 2.879
After features/support/hooks.rb:291 0.731
After features/support/hooks.rb:75 0.027
Tags: @product @automatic_upgrade
5:44.116
Before features/support/hooks.rb:245 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.710
And no SquashFS delta is installed 0.126
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.386
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.066
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.394
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.543
When the network is plugged 0.037
And Tor is ready 16.874
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.599
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.576
Given I shutdown Tails and wait for the computer to power off 7.302
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.453
Then Tails is running version 2.2~testoverlayfsng 0.107
And all tps features are active 2.573
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.395
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.309
# 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.336
When the network is plugged 0.037
And Tor is ready 17.480
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.711
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.510
Given I shutdown Tails and wait for the computer to power off 3.091
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:46.880
Then Tails is running version 2.3~testoverlayfsng 0.091
And all tps features are active 2.230
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.599
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.075
# 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.260
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.355
When the network is plugged 0.035
And Tor is ready 15.085
Then the Upgrader considers the system as up-to-date 0.285
# 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 25.350
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.165
After features/support/hooks.rb:291 0.752
After features/support/hooks.rb:75 0.023
Tags: @product @automatic_upgrade
28.392
Before features/support/hooks.rb:245 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.130
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.343
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.068
And the signing key used by the Upgrader is outdated 0.447
But a current signing key is available on our website 0.000
When the network is plugged 0.045
And Tor is ready 14.549
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.806
After features/support/hooks.rb:291 1.505
After features/support/hooks.rb:75 0.000