Project Number Date
test_Tails_ISO_stable 4559 08 Dec 2023, 12:12

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:58.032 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:25.159
Before features/support/hooks.rb:245 0.005
Given a computer 0.199
And I create a 7200 MiB disk named "old" 0.058
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 21.025
When I start Tails from USB drive "old" with network unplugged 58.689
Then the boot device has safe access rights 3.211
And Tails is running from USB drive "old" 0.321
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.066
And udev-watchdog is monitoring the correct device 0.257
And I unplug USB drive "old" 0.202
After features/support/hooks.rb:291 3.483
After features/support/hooks.rb:75 0.012
Tags: @product
1:59.310
Before features/support/hooks.rb:245 0.004
Given a computer 0.181
And I start Tails from USB drive "old" with network unplugged and I login 1:3.889
Then Tails is running from USB drive "old" 0.459
And I create a persistent partition 43.281
And I take note of which tps features are available 1.339
Then a Tails persistence partition exists on USB drive "old" 0.926
And I shutdown Tails and wait for the computer to power off 9.234
After features/support/hooks.rb:291 0.124
After features/support/hooks.rb:75 0.009
Tags: @product
2:19.816
Before features/support/hooks.rb:245 0.007
Given a computer 0.208
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:53.183
Then Tails is running from USB drive "old" 0.321
And all tps features are active 2.103
When I write some files expected to persist 1.816
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.223
And all persistence configuration files have safe access rights 0.577
And all persistent directories from the old Tails version have safe access rights 2.881
And I take note of which tps features are available 0.708
And I shutdown Tails and wait for the computer to power off 3.069
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.722
After features/support/hooks.rb:291 0.120
After features/support/hooks.rb:75 0.008
Tags: @product
2:31.888
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 10.485
And I log in to a new session 16.357
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.215
And I plug USB drive "to_upgrade" 2.548
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:47.565
Then the running Tails is installed on USB drive "to_upgrade" 13.317
And I unplug USB drive "to_upgrade" 0.214
And I unplug USB drive "__internal" 0.185
After features/support/hooks.rb:291 3.566
After features/support/hooks.rb:75 0.000
Tags: @product
2:4.523
Before features/support/hooks.rb:245 0.006
Given a computer 0.184
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:54.396
Then all tps features from the old Tails version are active 1.544
And Tails is running from USB drive "to_upgrade" 0.307
And the boot device has safe access rights 3.559
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 2.802
After features/support/hooks.rb:291 0.866
After features/support/hooks.rb:75 0.010
Tags: @product @automatic_upgrade
6:6.777
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.440
And no SquashFS delta is installed 0.121
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.322
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.080
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.356
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.539
When the network is plugged 0.063
And Tor is ready 19.346
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.955
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.716
Given I shutdown Tails and wait for the computer to power off 6.216
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.166
Then Tails is running version 2.2~testoverlayfsng 0.112
And all tps features are active 2.215
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.413
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.087
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.347
# 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.347
When the network is plugged 0.047
And Tor is ready 14.254
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.771
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 9.259
Given I shutdown Tails and wait for the computer to power off 4.277
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.213
Then Tails is running version 2.3~testoverlayfsng 0.142
And all tps features are active 2.286
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.650
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.074
# 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.336
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.336
When the network is plugged 0.034
And Tor is ready 19.047
Then the Upgrader considers the system as up-to-date 0.278
# 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 28.539
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.378
After features/support/hooks.rb:291 1.130
After features/support/hooks.rb:75 0.022
Tags: @product @automatic_upgrade
30.555
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 11.126
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.359
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.066
And the signing key used by the Upgrader is outdated 0.979
But a current signing key is available on our website 0.000
When the network is plugged 0.042
And Tor is ready 15.307
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.672
After features/support/hooks.rb:291 0.719
After features/support/hooks.rb:75 0.000