Project Number Date
test_Tails_ISO_stable 4518 16 Nov 2023, 12:13

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:47.836 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:34.973
Before features/support/hooks.rb:245 0.006
Given a computer 0.195
And I create a 7200 MiB disk named "old" 0.069
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 20.245
When I start Tails from USB drive "old" with network unplugged 1:9.579
Then the boot device has safe access rights 2.970
And Tails is running from USB drive "old" 0.303
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.053
And udev-watchdog is monitoring the correct device 0.257
And I unplug USB drive "old" 0.178
After features/support/hooks.rb:290 3.654
After features/support/hooks.rb:75 0.009
Tags: @product
1:58.842
Before features/support/hooks.rb:245 0.005
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login 1:6.449
Then Tails is running from USB drive "old" 0.386
And I create a persistent partition 42.270
And I take note of which tps features are available 1.512
Then a Tails persistence partition exists on USB drive "old" 0.916
And I shutdown Tails and wait for the computer to power off 7.123
After features/support/hooks.rb:290 0.132
After features/support/hooks.rb:75 0.012
Tags: @product
2:22.600
Before features/support/hooks.rb:245 0.007
Given a computer 0.199
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:48.381
Then Tails is running from USB drive "old" 0.337
And all tps features are active 8.400
When I write some files expected to persist 1.855
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.255
And all persistence configuration files have safe access rights 0.572
And all persistent directories from the old Tails version have safe access rights 2.660
And I take note of which tps features are available 0.559
And I shutdown Tails and wait for the computer to power off 3.068
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 16.310
After features/support/hooks.rb:290 0.143
After features/support/hooks.rb:75 0.009
Tags: @product
2:39.851
Before features/support/hooks.rb:245 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.864
And I log in to a new session 21.547
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.238
And I plug USB drive "to_upgrade" 2.424
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:50.563
Then the running Tails is installed on USB drive "to_upgrade" 13.815
And I unplug USB drive "to_upgrade" 0.198
And I unplug USB drive "__internal" 0.197
After features/support/hooks.rb:290 3.551
After features/support/hooks.rb:75 0.000
Tags: @product
2:11.197
Before features/support/hooks.rb:245 0.007
Given a computer 0.293
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:52.778
Then all tps features from the old Tails version are active 9.197
And Tails is running from USB drive "to_upgrade" 0.412
And the boot device has safe access rights 3.557
And the expected persistent files created with the old Tails version are present in the filesystem 1.898
And all persistent directories from the old Tails version have safe access rights 3.060
After features/support/hooks.rb:290 0.901
After features/support/hooks.rb:75 0.009
Tags: @product @automatic_upgrade
6:31.652
Before features/support/hooks.rb:245 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.579
And no SquashFS delta is installed 0.102
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.458
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.076
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.732
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.642
When the network is plugged 0.039
And Tor is ready 20.990
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.812
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.450
Given I shutdown Tails and wait for the computer to power off 7.274
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:50.948
Then Tails is running version 2.2~testoverlayfsng 0.091
And all tps features are active 10.198
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.440
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.310
# 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.435
When the network is plugged 0.053
And Tor is ready 17.248
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.926
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.896
Given I shutdown Tails and wait for the computer to power off 4.292
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.520
Then Tails is running version 2.3~testoverlayfsng 0.108
And all tps features are active 8.431
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.616
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.061
# 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.261
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.347
When the network is plugged 0.051
And Tor is ready 14.759
Then the Upgrader considers the system as up-to-date 10.770
# 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.483
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 2.175
After features/support/hooks.rb:290 0.798
After features/support/hooks.rb:75 0.026
Tags: @product @automatic_upgrade
28.719
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 10.454
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.355
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.058
And the signing key used by the Upgrader is outdated 1.774
But a current signing key is available on our website 0.000
When the network is plugged 0.061
And Tor is ready 14.228
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.785
After features/support/hooks.rb:290 0.725
After features/support/hooks.rb:75 0.000