Project Number Date
test_Tails_ISO_stable 5405 20 Jan 2025, 16:02

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:13.479 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:42.005
Before features/support/hooks.rb:269 0.004
Given a computer 0.245
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.061
And I write an old version of the Tails USB image to disk "old" 43.202
When I start Tails from USB drive "old" with network unplugged 1:53.062
Then the boot device has safe access rights 3.323
And Tails is running from USB drive "old" 0.373
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.110
And udev-watchdog is monitoring the correct device 0.297
And I unplug USB drive "old" 0.210
After features/support/hooks.rb:326 7.592
After features/support/hooks.rb:100 0.009
Tags: @product
2:19.333
Before features/support/hooks.rb:269 0.004
Given a computer 0.268
And I start Tails from USB drive "old" with network unplugged and I login 1:35.923
Then Tails is running from USB drive "old" 0.434
And I create a persistent partition 31.732
And I take note of which tps features are available 1.774
Then a Tails persistence partition exists on USB drive "old" 0.871
And I shutdown Tails and wait for the computer to power off 8.329
After features/support/hooks.rb:326 0.218
After features/support/hooks.rb:100 0.010
Tags: @product
2:58.548
Before features/support/hooks.rb:269 0.006
Given a computer 0.197
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.686
Then Tails is running from USB drive "old" 0.518
And all tps features are active 2.344
When I write some files expected to persist 1.963
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.307
And all persistence configuration files have safe access rights 0.622
And all persistent directories from the old Tails version have safe access rights 2.641
And I take note of which tps features are available 0.497
And I shutdown Tails and wait for the computer to power off 4.446
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.324
After features/support/hooks.rb:326 0.121
After features/support/hooks.rb:100 0.010
Tags: @product
2:33.103
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.416
And I log in to a new session 21.693
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.679
And I plug USB drive "to_upgrade" 2.357
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.560
Then the running Tails is installed on USB drive "to_upgrade" 21.879
And I unplug USB drive "to_upgrade" 0.257
And I unplug USB drive "__internal" 0.260
After features/support/hooks.rb:326 2.267
After features/support/hooks.rb:100 0.000
Tags: @product
2:22.876
Before features/support/hooks.rb:269 0.005
Given a computer 0.224
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.937
Then all tps features from the old Tails version are active 1.657
And Tails is running from USB drive "to_upgrade" 0.359
And the boot device has safe access rights 3.470
And the expected persistent files created with the old Tails version are present in the filesystem 1.470
And all persistent directories from the old Tails version have safe access rights 2.756
After features/support/hooks.rb:326 0.879
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:41.937
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.879
And no SquashFS delta is installed 0.090
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.361
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.364
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.801
When the network is plugged 0.068
And Tor is ready 22.195
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.931
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.439
Given I shutdown Tails and wait for the computer to power off 8.659
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.223
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.122
And the file system changes introduced in version 6.2~testoverlayfs are present 0.320
And only the 6.2~testoverlayfs SquashFS delta is installed 0.079
# 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.269
When the network is plugged 0.063
And Tor is ready 19.017
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.948
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.994
Given I shutdown Tails and wait for the computer to power off 4.513
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.046
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.133
And the file system changes introduced in version 6.3~testoverlayfs are present 0.649
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.564
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.298
When the network is plugged 0.132
And Tor is ready 19.261
Then the Upgrader considers the system as up-to-date 0.329
# 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.752
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.931
After features/support/hooks.rb:326 0.743
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
35.673
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.252
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.389
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.110
But a current signing key is available on our website 0.000
When the network is plugged 0.174
And Tor is ready 18.741
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.946
After features/support/hooks.rb:326 0.651
After features/support/hooks.rb:100 0.000