Project Number Date
test_Tails_ISO_stable 6100 29 Jan 2026, 12:08

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 12:22.541 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:44.014
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.051
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.902
When I start Tails from USB drive "old" with network unplugged 1:25.446
Then the boot device has safe access rights 2.926
And Tails is running from USB drive "old" 0.240
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.044
And udev-watchdog is monitoring the correct device 0.192
And I unplug USB drive "old" 0.138
After features/support/hooks.rb:331 3.874
After features/support/hooks.rb:100 0.031
Tags: @product
1:25.932
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login 51.956
Then Tails is running from USB drive "old" 0.230
And I create a persistent partition 24.222
And I take note of which tps features are available 0.672
Then a Tails persistence partition exists on USB drive "old" 0.523
And I shutdown Tails and wait for the computer to power off 8.275
After features/support/hooks.rb:331 0.500
After features/support/hooks.rb:100 0.007
Tags: @product
1:24.704
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.050
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.372
Then Tails is running from USB drive "old" 0.245
And all tps features are active 1.082
When I write some files expected to persist 1.234
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.160
And all persistence configuration files have safe access rights 0.344
And all persistent directories from the old Tails version have safe access rights 1.855
And I take note of which tps features are available 0.146
And I shutdown Tails and wait for the computer to power off 8.003
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.210
After features/support/hooks.rb:331 0.124
After features/support/hooks.rb:100 0.008
Tags: @product
2:21.788
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.645
And I log in to a new session 14.263
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.759
And I plug USB drive "to_upgrade" 2.245
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.537
Then the running Tails is installed on USB drive "to_upgrade" 15.939
And I unplug USB drive "to_upgrade" 0.154
And I unplug USB drive "__internal" 0.241
After features/support/hooks.rb:331 7.178
After features/support/hooks.rb:100 0.000
Tags: @product
1:8.568
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.069
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.027
Then all tps features from the old Tails version are active 0.979
And Tails is running from USB drive "to_upgrade" 0.250
And the boot device has safe access rights 2.371
And the expected persistent files created with the old Tails version are present in the filesystem 1.019
And all persistent directories from the old Tails version have safe access rights 1.850
After features/support/hooks.rb:331 0.656
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
3:55.820
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.564
And no SquashFS delta is installed 0.128
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.225
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.238
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.426
When the network is plugged 0.021
And Tor is ready 13.584
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.336
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.946
Given I shutdown Tails and wait for the computer to power off 21.284
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.390
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.093
And the file system changes introduced in version 6.2~testoverlayfs are present 0.247
And only the 6.2~testoverlayfs SquashFS delta is installed 0.039
# 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.195
When the network is plugged 0.017
And Tor is ready 9.902
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.103
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.801
Given I shutdown Tails and wait for the computer to power off 7.950
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.783
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.150
And the file system changes introduced in version 6.3~testoverlayfs are present 0.399
And only the 6.3~testoverlayfs SquashFS delta is installed 0.046
# 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.133
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.207
When the network is plugged 0.014
And Tor is ready 11.366
Then the Upgrader considers the system as up-to-date 10.523
# 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 4.098
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.368
After features/support/hooks.rb:331 0.774
After features/support/hooks.rb:100 0.038
Tags: @product @automatic_upgrade
21.713
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.562
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.224
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the signing key used by the Upgrader is outdated 0.072
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 10.819
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.980
After features/support/hooks.rb:331 1.032
After features/support/hooks.rb:100 0.000