Project Number Date
test_Tails_ISO_stable 5507 11 Mar 2025, 12:28

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 18:29.164 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:58.073
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.167
And I create a 7200 MiB disk named "old" 0.037
And I plug USB drive "old" 1.045
And I write an old version of the Tails USB image to disk "old" 30.902
When I start Tails from USB drive "old" with network unplugged 1:22.035
Then the boot device has safe access rights 2.882
And Tails is running from USB drive "old" 0.335
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.106
And udev-watchdog is monitoring the correct device 0.320
And I unplug USB drive "old" 0.173
After features/support/hooks.rb:330 3.508
After features/support/hooks.rb:100 0.031
Tags: @product
2:0.922
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.172
And I start Tails from USB drive "old" with network unplugged and I login 1:20.432
Then Tails is running from USB drive "old" 0.301
And I create a persistent partition 29.184
And I take note of which tps features are available 1.377
Then a Tails persistence partition exists on USB drive "old" 0.757
And I shutdown Tails and wait for the computer to power off 8.695
After features/support/hooks.rb:330 0.171
After features/support/hooks.rb:100 0.009
Tags: @product
2:45.213
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:9.572
Then Tails is running from USB drive "old" 0.393
And all tps features are active 1.770
When I write some files expected to persist 1.599
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.275
And all persistence configuration files have safe access rights 0.527
And all persistent directories from the old Tails version have safe access rights 2.326
And I take note of which tps features are available 0.387
And I shutdown Tails and wait for the computer to power off 4.301
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.870
After features/support/hooks.rb:330 0.109
After features/support/hooks.rb:100 0.009
Tags: @product
2:24.916
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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.113
And I log in to a new session 17.929
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.501
And I plug USB drive "to_upgrade" 2.382
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.841
Then the running Tails is installed on USB drive "to_upgrade" 19.698
And I unplug USB drive "to_upgrade" 0.227
And I unplug USB drive "__internal" 0.221
After features/support/hooks.rb:330 1.805
After features/support/hooks.rb:100 0.000
Tags: @product
2:9.108
Before features/support/hooks.rb:266 0.001
Before features/support/hooks.rb:273 0.006
Given a computer 0.170
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:0.190
Then all tps features from the old Tails version are active 1.513
And Tails is running from USB drive "to_upgrade" 0.306
And the boot device has safe access rights 3.064
And the expected persistent files created with the old Tails version are present in the filesystem 1.548
And all persistent directories from the old Tails version have safe access rights 2.313
After features/support/hooks.rb:330 1.181
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:34.484
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.736
And no SquashFS delta is installed 0.069
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.398
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.257
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.410
When the network is plugged 0.058
And Tor is ready 25.017
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.853
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.782
Given I shutdown Tails and wait for the computer to power off 8.553
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.281
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.124
And the file system changes introduced in version 6.2~testoverlayfs are present 0.302
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.328
# 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.466
When the network is plugged 0.064
And Tor is ready 20.411
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.434
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.812
Given I shutdown Tails and wait for the computer to power off 4.339
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.904
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 1.904
And the file system changes introduced in version 6.3~testoverlayfs are present 0.478
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.296
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.270
When the network is plugged 0.070
And Tor is ready 16.641
Then the Upgrader considers the system as up-to-date 0.337
# 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.551
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.095
After features/support/hooks.rb:330 0.890
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
36.446
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.440
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.447
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.086
And the signing key used by the Upgrader is outdated 0.097
But a current signing key is available on our website 0.000
When the network is plugged 0.076
And Tor is ready 19.049
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.248
After features/support/hooks.rb:330 0.902
After features/support/hooks.rb:100 0.000