Project Number Date
test_Tails_ISO_stable 4660 10 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:19.536 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:29.650
Before features/support/hooks.rb:245 0.006
Given a computer 0.177
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 20.631
When I start Tails from USB drive "old" with network unplugged 1:3.461
Then the boot device has safe access rights 3.263
And Tails is running from USB drive "old" 0.355
And there is no persistence partition on USB drive "old" 0.085
And process "udev-watchdog" is running 0.063
And udev-watchdog is monitoring the correct device 0.293
And I unplug USB drive "old" 0.227
After features/support/hooks.rb:291 3.551
After features/support/hooks.rb:75 0.008
Tags: @product
2:1.893
Before features/support/hooks.rb:245 0.005
Given a computer 0.172
And I start Tails from USB drive "old" with network unplugged and I login 1:7.055
Then Tails is running from USB drive "old" 0.493
And I create a persistent partition 43.126
And I take note of which tps features are available 1.484
Then a Tails persistence partition exists on USB drive "old" 2.492
And I shutdown Tails and wait for the computer to power off 7.068
After features/support/hooks.rb:291 0.174
After features/support/hooks.rb:75 0.010
Tags: @product
2:29.871
Before features/support/hooks.rb:245 0.006
Given a computer 0.205
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:0.564
Then Tails is running from USB drive "old" 0.330
And all tps features are active 2.121
When I write some files expected to persist 1.909
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.304
And all persistence configuration files have safe access rights 0.713
And all persistent directories from the old Tails version have safe access rights 2.997
And I take note of which tps features are available 0.544
And I shutdown Tails and wait for the computer to power off 3.352
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 16.828
After features/support/hooks.rb:291 0.133
After features/support/hooks.rb:75 0.012
Tags: @product
2:33.495
Before features/support/hooks.rb:245 0.009
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.870
And I log in to a new session 17.108
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.235
And I plug USB drive "to_upgrade" 2.415
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:48.727
Then the running Tails is installed on USB drive "to_upgrade" 12.772
And I unplug USB drive "to_upgrade" 0.195
And I unplug USB drive "__internal" 0.169
After features/support/hooks.rb:291 6.849
After features/support/hooks.rb:75 0.000
Tags: @product
2:7.236
Before features/support/hooks.rb:245 0.017
Given a computer 0.165
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:57.151
Then all tps features from the old Tails version are active 1.578
And Tails is running from USB drive "to_upgrade" 0.368
And the boot device has safe access rights 3.588
And the expected persistent files created with the old Tails version are present in the filesystem 1.634
And all persistent directories from the old Tails version have safe access rights 2.747
After features/support/hooks.rb:291 0.689
After features/support/hooks.rb:75 0.009
Tags: @product @automatic_upgrade
6:9.881
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.455
And no SquashFS delta is installed 0.102
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.357
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.077
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.443
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.551
When the network is plugged 0.028
And Tor is ready 14.686
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.648
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.635
Given I shutdown Tails and wait for the computer to power off 6.531
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.991
Then Tails is running version 2.2~testoverlayfsng 0.108
And all tps features are active 2.476
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.371
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.367
# 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.281
When the network is plugged 0.034
And Tor is ready 17.720
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 3.206
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.073
Given I shutdown Tails and wait for the computer to power off 4.282
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.068
Then Tails is running version 2.3~testoverlayfsng 0.126
And all tps features are active 1.916
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.581
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.069
# 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.320
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.309
When the network is plugged 0.041
And Tor is ready 15.756
Then the Upgrader considers the system as up-to-date 0.292
# 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 29.602
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.306
After features/support/hooks.rb:291 0.727
After features/support/hooks.rb:75 0.049
Tags: @product @automatic_upgrade
27.508
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.086
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.356
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.064
And the signing key used by the Upgrader is outdated 0.567
But a current signing key is available on our website 0.000
When the network is plugged 0.034
And Tor is ready 15.749
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.648
After features/support/hooks.rb:291 0.688
After features/support/hooks.rb:75 0.000