Project Number Date
test_Tails_ISO_stable 4603 06 Jan 2024, 12:33

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:12.781 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:32.046
Before features/support/hooks.rb:245 0.007
Given a computer 0.185
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 23.933
When I start Tails from USB drive "old" with network unplugged 1:2.312
Then the boot device has safe access rights 3.487
And Tails is running from USB drive "old" 0.358
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.064
And udev-watchdog is monitoring the correct device 0.296
And I unplug USB drive "old" 0.218
After features/support/hooks.rb:291 3.583
After features/support/hooks.rb:75 0.013
Tags: @product
2:3.395
Before features/support/hooks.rb:245 0.007
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login 1:5.536
Then Tails is running from USB drive "old" 0.498
And I create a persistent partition 46.153
And I take note of which tps features are available 1.968
Then a Tails persistence partition exists on USB drive "old" 0.963
And I shutdown Tails and wait for the computer to power off 8.076
After features/support/hooks.rb:291 0.184
After features/support/hooks.rb:75 0.010
Tags: @product
2:29.058
Before features/support/hooks.rb:245 0.006
Given a computer 0.196
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:0.605
Then Tails is running from USB drive "old" 0.497
And all tps features are active 2.284
When I write some files expected to persist 2.221
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.293
And all persistence configuration files have safe access rights 0.661
And all persistent directories from the old Tails version have safe access rights 2.688
And I take note of which tps features are available 0.542
And I shutdown Tails and wait for the computer to power off 3.074
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.993
After features/support/hooks.rb:291 0.145
After features/support/hooks.rb:75 0.010
Tags: @product
2:41.576
Before features/support/hooks.rb:245 0.020
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.395
And I log in to a new session 22.062
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.646
And I plug USB drive "to_upgrade" 2.736
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:50.010
Then the running Tails is installed on USB drive "to_upgrade" 14.252
And I unplug USB drive "to_upgrade" 0.251
And I unplug USB drive "__internal" 0.222
After features/support/hooks.rb:291 7.049
After features/support/hooks.rb:75 0.000
Tags: @product
2:5.421
Before features/support/hooks.rb:245 0.007
Given a computer 0.208
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:53.587
Then all tps features from the old Tails version are active 1.986
And Tails is running from USB drive "to_upgrade" 0.428
And the boot device has safe access rights 4.432
And the expected persistent files created with the old Tails version are present in the filesystem 1.729
And all persistent directories from the old Tails version have safe access rights 3.049
After features/support/hooks.rb:291 0.768
After features/support/hooks.rb:75 0.011
Tags: @product @automatic_upgrade
5:51.647
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 11.465
And no SquashFS delta is installed 0.080
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.271
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.068
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.470
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.591
When the network is plugged 0.040
And Tor is ready 17.293
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.805
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.052
Given I shutdown Tails and wait for the computer to power off 6.561
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.034
Then Tails is running version 2.2~testoverlayfsng 0.113
And all tps features are active 2.428
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.368
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.094
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.276
# 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.032
And Tor is ready 15.519
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.657
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.777
Given I shutdown Tails and wait for the computer to power off 3.343
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:50.465
Then Tails is running version 2.3~testoverlayfsng 0.144
And all tps features are active 2.126
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.064
# 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.294
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.299
When the network is plugged 0.056
And Tor is ready 14.567
Then the Upgrader considers the system as up-to-date 0.268
# 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 27.838
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 2.264
After features/support/hooks.rb:291 0.751
After features/support/hooks.rb:75 0.071
Tags: @product @automatic_upgrade
29.636
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 10.266
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.446
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.080
And the signing key used by the Upgrader is outdated 0.825
But a current signing key is available on our website 0.000
When the network is plugged 0.046
And Tor is ready 15.176
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.794
After features/support/hooks.rb:291 1.418
After features/support/hooks.rb:75 0.000