Project Number Date
test_Tails_ISO_stable 5345 18 Dec 2024, 19:23

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 20:5.384 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:14.951
Before features/support/hooks.rb:269 0.006
Given a computer 0.206
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 30.909
When I start Tails from USB drive "old" with network unplugged 1:38.329
Then the boot device has safe access rights 3.160
And Tails is running from USB drive "old" 0.321
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.104
And udev-watchdog is monitoring the correct device 0.526
And I unplug USB drive "old" 0.223
After features/support/hooks.rb:326 3.659
After features/support/hooks.rb:100 0.009
Tags: @product
2:18.825
Before features/support/hooks.rb:269 0.006
Given a computer 0.181
And I start Tails from USB drive "old" with network unplugged and I login 1:34.734
Then Tails is running from USB drive "old" 0.372
And I create a persistent partition 32.423
And I take note of which tps features are available 1.851
Then a Tails persistence partition exists on USB drive "old" 0.796
And I shutdown Tails and wait for the computer to power off 8.467
After features/support/hooks.rb:326 0.233
After features/support/hooks.rb:100 0.012
Tags: @product
3:10.448
Before features/support/hooks.rb:269 0.006
Given a computer 0.189
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:32.246
Then Tails is running from USB drive "old" 1.125
And all tps features are active 2.183
When I write some files expected to persist 1.852
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.330
And all persistence configuration files have safe access rights 0.608
And all persistent directories from the old Tails version have safe access rights 2.613
And I take note of which tps features are available 0.455
And I shutdown Tails and wait for the computer to power off 4.244
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.599
After features/support/hooks.rb:326 0.167
After features/support/hooks.rb:100 0.009
Tags: @product
2:35.460
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 11.649
And I log in to a new session 22.515
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.948
And I plug USB drive "to_upgrade" 2.476
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.466
Then the running Tails is installed on USB drive "to_upgrade" 20.940
And I unplug USB drive "to_upgrade" 0.229
And I unplug USB drive "__internal" 0.232
After features/support/hooks.rb:326 2.670
After features/support/hooks.rb:100 0.000
Tags: @product
2:25.946
Before features/support/hooks.rb:269 0.008
Given a computer 0.194
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:16.610
Then all tps features from the old Tails version are active 1.674
And Tails is running from USB drive "to_upgrade" 0.352
And the boot device has safe access rights 3.276
And the expected persistent files created with the old Tails version are present in the filesystem 1.501
And all persistent directories from the old Tails version have safe access rights 2.336
After features/support/hooks.rb:326 0.834
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:43.320
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.263
And no SquashFS delta is installed 0.098
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.344
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.320
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.513
When the network is plugged 0.068
And Tor is ready 22.422
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.182
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.570
Given I shutdown Tails and wait for the computer to power off 8.929
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.979
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.056
And the file system changes introduced in version 6.2~testoverlayfs are present 0.297
And only the 6.2~testoverlayfs SquashFS delta is installed 0.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.345
# 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.332
When the network is plugged 0.064
And Tor is ready 21.580
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.948
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.402
Given I shutdown Tails and wait for the computer to power off 4.398
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.516
Then Tails is running version 6.3~testoverlayfs 0.035
And all tps features are active 1.993
And the file system changes introduced in version 6.3~testoverlayfs are present 0.494
And only the 6.3~testoverlayfs SquashFS delta is installed 0.057
# 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.269
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.339
When the network is plugged 0.084
And Tor is ready 18.426
Then the Upgrader considers the system as up-to-date 10.834
# 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 14.040
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.948
After features/support/hooks.rb:326 0.924
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
36.431
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.057
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.338
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the signing key used by the Upgrader is outdated 0.754
But a current signing key is available on our website 0.000
When the network is plugged 0.074
And Tor is ready 18.458
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.682
After features/support/hooks.rb:326 1.478
After features/support/hooks.rb:100 0.000