Project Number Date
test_Tails_ISO_stable 4627 21 Jan 2024, 13:10

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 15:37.125 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:19.088
Before features/support/hooks.rb:245 0.006
Given a computer 0.132
And I create a 7200 MiB disk named "old" 0.027
And I plug USB drive "old" 1.041
And I write an old version of the Tails USB image to disk "old" 18.416
When I start Tails from USB drive "old" with network unplugged 55.803
Then the boot device has safe access rights 2.823
And Tails is running from USB drive "old" 0.297
And there is no persistence partition on USB drive "old" 0.060
And process "udev-watchdog" is running 0.061
And udev-watchdog is monitoring the correct device 0.243
And I unplug USB drive "old" 0.180
After features/support/hooks.rb:291 3.477
After features/support/hooks.rb:75 0.010
Tags: @product
1:51.960
Before features/support/hooks.rb:245 0.006
Given a computer 0.142
And I start Tails from USB drive "old" with network unplugged and I login 1:1.984
Then Tails is running from USB drive "old" 0.305
And I create a persistent partition 40.402
And I take note of which tps features are available 1.220
Then a Tails persistence partition exists on USB drive "old" 0.847
And I shutdown Tails and wait for the computer to power off 7.057
After features/support/hooks.rb:291 0.105
After features/support/hooks.rb:75 0.010
Tags: @product
2:7.080
Before features/support/hooks.rb:245 0.006
Given a computer 0.156
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:41.733
Then Tails is running from USB drive "old" 0.321
And all tps features are active 1.675
When I write some files expected to persist 1.737
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.258
And all persistence configuration files have safe access rights 0.639
And all persistent directories from the old Tails version have safe access rights 2.481
And I take note of which tps features are available 0.281
And I shutdown Tails and wait for the computer to power off 3.071
# 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.110
After features/support/hooks.rb:75 0.011
Tags: @product
2:30.496
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 10.141
And I log in to a new session 15.294
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.027
And I plug USB drive "to_upgrade" 2.466
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:49.276
Then the running Tails is installed on USB drive "to_upgrade" 11.939
And I unplug USB drive "to_upgrade" 0.184
And I unplug USB drive "__internal" 0.165
After features/support/hooks.rb:291 0.946
After features/support/hooks.rb:75 0.000
Tags: @product
1:51.620
Before features/support/hooks.rb:245 0.007
Given a computer 0.143
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:41.693
Then all tps features from the old Tails version are active 1.436
And Tails is running from USB drive "to_upgrade" 0.333
And the boot device has safe access rights 3.429
And the expected persistent files created with the old Tails version are present in the filesystem 1.510
And all persistent directories from the old Tails version have safe access rights 3.072
After features/support/hooks.rb:291 0.645
After features/support/hooks.rb:75 0.025
Tags: @product @automatic_upgrade
5:31.214
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.443
And no SquashFS delta is installed 0.083
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.267
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.059
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.328
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.492
When the network is plugged 0.024
And Tor is ready 16.177
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.568
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 7.709
Given I shutdown Tails and wait for the computer to power off 5.090
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:40.899
Then Tails is running version 2.2~testoverlayfsng 0.083
And all tps features are active 1.835
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.369
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.272
# 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.263
When the network is plugged 0.029
And Tor is ready 14.729
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.557
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.721
Given I shutdown Tails and wait for the computer to power off 4.078
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:48.423
Then Tails is running version 2.3~testoverlayfsng 0.084
And all tps features are active 1.649
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.606
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.063
# 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.394
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.289
When the network is plugged 0.023
And Tor is ready 15.435
Then the Upgrader considers the system as up-to-date 0.276
# 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.457
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.338
After features/support/hooks.rb:291 0.791
After features/support/hooks.rb:75 0.021
Tags: @product @automatic_upgrade
25.665
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.004
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.315
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 0.553
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 15.164
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 0.547
After features/support/hooks.rb:291 1.066
After features/support/hooks.rb:75 0.000