Project Number Date
test_Tails_ISO_devel 4125 17 Dec 2025, 15: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 14:36.349 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:42.465
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 4.183
And I create a 7200 MiB disk named "old" 0.081
And I plug USB drive "old" 1.040
And I write an old version of the Tails USB image to disk "old" 34.045
When I start Tails from USB drive "old" with network unplugged 59.064
Then the boot device has safe access rights 3.144
And Tails is running from USB drive "old" 0.320
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.277
And I unplug USB drive "old" 0.189
After features/support/hooks.rb:331 4.056
After features/support/hooks.rb:100 0.058
Tags: @product
1:48.174
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.027
Given a computer 0.585
And I start Tails from USB drive "old" with network unplugged and I login 1:5.554
Then Tails is running from USB drive "old" 0.834
And I create a persistent partition 30.339
And I take note of which tps features are available 1.416
Then a Tails persistence partition exists on USB drive "old" 0.766
And I shutdown Tails and wait for the computer to power off 8.676
After features/support/hooks.rb:331 0.305
After features/support/hooks.rb:100 0.009
Tags: @product
1:57.089
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:20.927
Then Tails is running from USB drive "old" 0.639
And all tps features are active 1.981
When I write some files expected to persist 1.502
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.174
And all persistence configuration files have safe access rights 0.385
And all persistent directories from the old Tails version have safe access rights 2.357
And I take note of which tps features are available 0.455
And I shutdown Tails and wait for the computer to power off 8.347
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 20.124
After features/support/hooks.rb:331 0.456
After features/support/hooks.rb:100 0.009
Tags: @product
2:38.410
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 without a persistent partition and stopped at Tails Greeter's login screen 11.476
And I log in to a new session 17.355
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.381
And I plug USB drive "to_upgrade" 2.730
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:43.827
Then the running Tails is installed on USB drive "to_upgrade" 21.027
And I unplug USB drive "to_upgrade" 0.356
And I unplug USB drive "__internal" 0.255
After features/support/hooks.rb:331 0.887
After features/support/hooks.rb:100 0.000
Tags: @product
1:28.039
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.198
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:18.262
Then all tps features from the old Tails version are active 2.113
And Tails is running from USB drive "to_upgrade" 0.456
And the boot device has safe access rights 3.331
And the expected persistent files created with the old Tails version are present in the filesystem 1.514
And all persistent directories from the old Tails version have safe access rights 2.161
After features/support/hooks.rb:331 0.851
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
4:37.096
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 13.675
And no SquashFS delta is installed 0.104
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.080
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.396
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.534
When the network is plugged 0.078
And Tor is ready 14.778
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.839
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.650
Given I shutdown Tails and wait for the computer to power off 11.785
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:25.214
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.443
And the file system changes introduced in version 6.2~testoverlayfs are present 0.306
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.177
# 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.282
When the network is plugged 0.071
And Tor is ready 13.817
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.018
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.105
Given I shutdown Tails and wait for the computer to power off 9.045
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:22.200
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 2.442
And the file system changes introduced in version 6.3~testoverlayfs are present 0.419
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.150
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.226
When the network is plugged 0.050
And Tor is ready 12.232
Then the Upgrader considers the system as up-to-date 0.160
# 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 5.838
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.475
After features/support/hooks.rb:331 0.750
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
25.074
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 10.771
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.352
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 0.087
But a current signing key is available on our website 0.000
When the network is plugged 0.071
And Tor is ready 11.938
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.799
After features/support/hooks.rb:331 1.016
After features/support/hooks.rb:100 0.000