Project Number Date
test_Tails_ISO_stable 5128 30 Sep 2024, 18:45

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 19:34.397 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
2:6.925
Before features/support/hooks.rb:269 0.005
Given a computer 0.176
And I create a 7200 MiB disk named "old" 0.039
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 34.022
When I start Tails from USB drive "old" with network unplugged 1:27.442
Then the boot device has safe access rights 3.193
And Tails is running from USB drive "old" 0.356
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.103
And udev-watchdog is monitoring the correct device 0.283
And I unplug USB drive "old" 0.199
After features/support/hooks.rb:326 7.447
After features/support/hooks.rb:100 0.011
Tags: @product
2:16.841
Before features/support/hooks.rb:269 0.007
Given a computer 0.460
And I start Tails from USB drive "old" with network unplugged and I login 1:33.183
Then Tails is running from USB drive "old" 0.308
And I create a persistent partition 32.128
And I take note of which tps features are available 1.553
Then a Tails persistence partition exists on USB drive "old" 0.843
And I shutdown Tails and wait for the computer to power off 8.363
After features/support/hooks.rb:326 0.191
After features/support/hooks.rb:100 0.009
Tags: @product
2:50.980
Before features/support/hooks.rb:269 0.006
Given a computer 0.176
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.382
Then Tails is running from USB drive "old" 1.189
And all tps features are active 1.863
When I write some files expected to persist 3.227
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.221
And all persistence configuration files have safe access rights 0.421
And all persistent directories from the old Tails version have safe access rights 2.581
And I take note of which tps features are available 0.464
And I shutdown Tails and wait for the computer to power off 4.378
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.075
After features/support/hooks.rb:326 0.145
After features/support/hooks.rb:100 0.010
Tags: @product
2:28.440
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.815
And I log in to a new session 17.866
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.056
And I plug USB drive "to_upgrade" 2.548
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.728
Then the running Tails is installed on USB drive "to_upgrade" 21.012
And I unplug USB drive "to_upgrade" 0.213
And I unplug USB drive "__internal" 0.199
After features/support/hooks.rb:326 2.124
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.701
Before features/support/hooks.rb:269 0.006
Given a computer 0.190
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.951
Then all tps features from the old Tails version are active 1.780
And Tails is running from USB drive "to_upgrade" 0.346
And the boot device has safe access rights 3.259
And the expected persistent files created with the old Tails version are present in the filesystem 1.451
And all persistent directories from the old Tails version have safe access rights 2.721
After features/support/hooks.rb:326 0.695
After features/support/hooks.rb:100 0.026
Tags: @product @automatic_upgrade
6:55.810
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.090
And no SquashFS delta is installed 0.401
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.520
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.084
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.352
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.446
When the network is plugged 0.090
And Tor is ready 20.930
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.733
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.887
Given I shutdown Tails and wait for the computer to power off 13.788
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.085
Then Tails is running version 6.2~testoverlayfs 0.040
And all tps features are active 2.318
And the file system changes introduced in version 6.2~testoverlayfs are present 0.310
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.322
# We'll really install Tails_amd64_6.0~testoverlayfs_to_6.3~testoverlayfs.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 6.1~testoverlayfs was initially installed 0.300
When the network is plugged 0.070
And Tor is ready 47.430
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.665
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.547
Given I shutdown Tails and wait for the computer to power off 4.417
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.635
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.242
And the file system changes introduced in version 6.3~testoverlayfs are present 0.481
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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 6.1~testoverlayfs was initially installed 0.320
When the network is plugged 0.075
And Tor is ready 17.631
Then the Upgrader considers the system as up-to-date 0.320
# 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 13.835
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.946
After features/support/hooks.rb:326 0.772
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
37.697
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.363
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.450
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.076
And the signing key used by the Upgrader is outdated 1.036
But a current signing key is available on our website 0.000
When the network is plugged 0.073
And Tor is ready 19.188
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.508
After features/support/hooks.rb:326 0.909
After features/support/hooks.rb:100 0.000