Project Number Date
test_Tails_ISO_devel 3689 13 Feb 2025, 12:53

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:34.600 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:25.951
Before features/support/hooks.rb:269 0.005
Given a computer 0.262
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 29.925
When I start Tails from USB drive "old" with network unplugged 1:50.277
Then the boot device has safe access rights 3.319
And Tails is running from USB drive "old" 0.347
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.110
And udev-watchdog is monitoring the correct device 0.355
And I unplug USB drive "old" 0.194
After features/support/hooks.rb:326 7.042
After features/support/hooks.rb:100 0.009
Tags: @product
2:20.810
Before features/support/hooks.rb:269 0.007
Given a computer 0.275
And I start Tails from USB drive "old" with network unplugged and I login 1:36.430
Then Tails is running from USB drive "old" 0.327
And I create a persistent partition 32.819
And I take note of which tps features are available 1.605
Then a Tails persistence partition exists on USB drive "old" 0.886
And I shutdown Tails and wait for the computer to power off 8.464
After features/support/hooks.rb:326 0.250
After features/support/hooks.rb:100 0.010
Tags: @product
3:0.581
Before features/support/hooks.rb:269 0.006
Given a computer 0.199
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.247
Then Tails is running from USB drive "old" 0.490
And all tps features are active 2.079
When I write some files expected to persist 1.979
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.268
And all persistence configuration files have safe access rights 0.551
And all persistent directories from the old Tails version have safe access rights 2.806
And I take note of which tps features are available 0.504
And I shutdown Tails and wait for the computer to power off 4.140
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.314
After features/support/hooks.rb:326 0.170
After features/support/hooks.rb:100 0.013
Tags: @product
2:33.453
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 12.248
And I log in to a new session 21.409
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.833
And I plug USB drive "to_upgrade" 2.476
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.057
Then the running Tails is installed on USB drive "to_upgrade" 19.947
And I unplug USB drive "to_upgrade" 0.257
And I unplug USB drive "__internal" 0.224
After features/support/hooks.rb:326 2.753
After features/support/hooks.rb:100 0.000
Tags: @product
2:27.034
Before features/support/hooks.rb:269 0.007
Given a computer 0.216
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:16.405
Then all tps features from the old Tails version are active 2.008
And Tails is running from USB drive "to_upgrade" 0.478
And the boot device has safe access rights 3.512
And the expected persistent files created with the old Tails version are present in the filesystem 1.664
And all persistent directories from the old Tails version have safe access rights 2.748
After features/support/hooks.rb:326 1.060
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:10.336
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 12.959
And no SquashFS delta is installed 0.133
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.340
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.322
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.714
When the network is plugged 0.082
And Tor is ready 20.706
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.946
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.322
Given I shutdown Tails and wait for the computer to power off 9.543
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:21.187
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.446
And the file system changes introduced in version 6.2~testoverlayfs are present 0.318
And only the 6.2~testoverlayfs SquashFS delta is installed 0.100
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.334
# 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.336
When the network is plugged 0.091
And Tor is ready 46.338
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.635
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.291
Given I shutdown Tails and wait for the computer to power off 4.648
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.539
Then Tails is running version 6.3~testoverlayfs 0.020
And all tps features are active 2.402
And the file system changes introduced in version 6.3~testoverlayfs are present 0.502
And only the 6.3~testoverlayfs SquashFS delta is installed 0.088
# 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.319
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.288
When the network is plugged 0.075
And Tor is ready 16.286
Then the Upgrader considers the system as up-to-date 0.341
# 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 16.481
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.112
After features/support/hooks.rb:326 0.794
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
36.431
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 11.276
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.540
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.074
And the signing key used by the Upgrader is outdated 0.071
But a current signing key is available on our website 0.000
When the network is plugged 0.084
And Tor is ready 17.385
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.999
After features/support/hooks.rb:326 1.033
After features/support/hooks.rb:100 0.000