Project Number Date
test_Tails_ISO_stable 4664 13 Feb 2024, 23:32

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:47.936 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:21.985
Before features/support/hooks.rb:245 0.004
Given a computer 0.140
And I create a 7200 MiB disk named "old" 0.028
And I plug USB drive "old" 1.041
And I write an old version of the Tails USB image to disk "old" 19.570
When I start Tails from USB drive "old" with network unplugged 57.357
Then the boot device has safe access rights 2.959
And Tails is running from USB drive "old" 0.344
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.055
And udev-watchdog is monitoring the correct device 0.236
And I unplug USB drive "old" 0.188
After features/support/hooks.rb:291 3.528
After features/support/hooks.rb:75 0.027
Tags: @product
1:56.900
Before features/support/hooks.rb:245 0.005
Given a computer 0.166
And I start Tails from USB drive "old" with network unplugged and I login 1:3.178
Then Tails is running from USB drive "old" 0.475
And I create a persistent partition 43.645
And I take note of which tps features are available 1.458
Then a Tails persistence partition exists on USB drive "old" 0.901
And I shutdown Tails and wait for the computer to power off 7.075
After features/support/hooks.rb:291 0.109
After features/support/hooks.rb:75 0.010
Tags: @product
2:15.348
Before features/support/hooks.rb:245 0.006
Given a computer 0.182
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:48.462
Then Tails is running from USB drive "old" 0.358
And all tps features are active 2.069
When I write some files expected to persist 1.906
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.208
And all persistence configuration files have safe access rights 0.438
And all persistent directories from the old Tails version have safe access rights 2.976
And I take note of which tps features are available 0.350
And I shutdown Tails and wait for the computer to power off 3.067
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.328
After features/support/hooks.rb:291 0.111
After features/support/hooks.rb:75 0.013
Tags: @product
2:40.892
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.544
And I log in to a new session 22.068
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.283
And I plug USB drive "to_upgrade" 2.526
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:50.383
Then the running Tails is installed on USB drive "to_upgrade" 12.648
And I unplug USB drive "to_upgrade" 0.207
And I unplug USB drive "__internal" 0.229
After features/support/hooks.rb:291 0.810
After features/support/hooks.rb:75 0.000
Tags: @product
2:5.798
Before features/support/hooks.rb:245 0.008
Given a computer 0.166
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:54.567
Then all tps features from the old Tails version are active 1.768
And Tails is running from USB drive "to_upgrade" 0.388
And the boot device has safe access rights 3.687
And the expected persistent files created with the old Tails version are present in the filesystem 2.065
And all persistent directories from the old Tails version have safe access rights 3.154
After features/support/hooks.rb:291 0.748
After features/support/hooks.rb:75 0.013
Tags: @product @automatic_upgrade
5:58.595
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 16.966
And no SquashFS delta is installed 0.128
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.410
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.085
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.438
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.715
When the network is plugged 0.024
And Tor is ready 15.603
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.906
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.343
Given I shutdown Tails and wait for the computer to power off 8.474
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.914
Then Tails is running version 2.2~testoverlayfsng 0.108
And all tps features are active 1.873
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.493
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.093
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.306
# 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.353
When the network is plugged 0.024
And Tor is ready 17.453
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.790
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 9.255
Given I shutdown Tails and wait for the computer to power off 4.472
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:46.168
Then Tails is running version 2.3~testoverlayfsng 0.168
And all tps features are active 2.558
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.541
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.244
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.318
When the network is plugged 0.091
And Tor is ready 16.367
Then the Upgrader considers the system as up-to-date 0.335
# 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.086
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.413
After features/support/hooks.rb:291 0.718
After features/support/hooks.rb:75 0.022
Tags: @product @automatic_upgrade
28.416
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 9.766
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.469
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.083
And the signing key used by the Upgrader is outdated 0.464
But a current signing key is available on our website 0.000
When the network is plugged 0.034
And Tor is ready 15.975
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.622
After features/support/hooks.rb:291 0.663
After features/support/hooks.rb:75 0.000