Project Number Date
test_Tails_ISO_devel 4229 12 Feb 2026, 11:56

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 11:34.574 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:14.862
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.067
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 14.204
When I start Tails from USB drive "old" with network unplugged 55.853
Then the boot device has safe access rights 2.982
And Tails is running from USB drive "old" 0.263
And there is no persistence partition on USB drive "old" 0.051
And process "udev-watchdog" is running 0.071
And udev-watchdog is monitoring the correct device 0.196
And I unplug USB drive "old" 0.144
After features/support/hooks.rb:331 1.205
After features/support/hooks.rb:100 0.007
Tags: @product
1:26.993
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.062
And I start Tails from USB drive "old" with network unplugged and I login 53.494
Then Tails is running from USB drive "old" 0.339
And I create a persistent partition 23.620
And I take note of which tps features are available 0.744
Then a Tails persistence partition exists on USB drive "old" 0.550
And I shutdown Tails and wait for the computer to power off 8.182
After features/support/hooks.rb:331 0.417
After features/support/hooks.rb:100 0.013
Tags: @product
1:25.983
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.057
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.541
Then Tails is running from USB drive "old" 0.273
And all tps features are active 1.283
When I write some files expected to persist 1.328
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.190
And all persistence configuration files have safe access rights 0.333
And all persistent directories from the old Tails version have safe access rights 2.177
And I take note of which tps features are available 0.153
And I shutdown Tails and wait for the computer to power off 3.955
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.689
After features/support/hooks.rb:331 0.378
After features/support/hooks.rb:100 0.007
Tags: @product
2:12.237
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.192
And I log in to a new session 11.257
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.744
And I plug USB drive "to_upgrade" 2.258
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.594
Then the running Tails is installed on USB drive "to_upgrade" 15.934
And I unplug USB drive "to_upgrade" 0.123
And I unplug USB drive "__internal" 0.130
After features/support/hooks.rb:331 2.499
After features/support/hooks.rb:100 0.000
Tags: @product
1:10.087
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.049
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.558
Then all tps features from the old Tails version are active 0.986
And Tails is running from USB drive "to_upgrade" 0.260
And the boot device has safe access rights 2.830
And the expected persistent files created with the old Tails version are present in the filesystem 1.292
And all persistent directories from the old Tails version have safe access rights 2.110
After features/support/hooks.rb:331 0.612
After features/support/hooks.rb:100 0.034
Tags: @product @automatic_upgrade
3:43.392
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.081
And no SquashFS delta is installed 0.070
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.283
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.380
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.438
When the network is plugged 0.025
And Tor is ready 13.802
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.950
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.139
Given I shutdown Tails and wait for the computer to power off 9.611
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.410
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.240
And the file system changes introduced in version 6.2~testoverlayfs are present 0.282
And only the 6.2~testoverlayfs SquashFS delta is installed 0.048
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.148
# 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.205
When the network is plugged 0.022
And Tor is ready 10.526
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.937
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.923
Given I shutdown Tails and wait for the computer to power off 8.234
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.050
Then Tails is running version 6.3~testoverlayfs 0.023
And all tps features are active 1.199
And the file system changes introduced in version 6.3~testoverlayfs are present 0.372
And only the 6.3~testoverlayfs SquashFS delta is installed 0.047
# 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.185
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.227
When the network is plugged 0.014
And Tor is ready 10.675
Then the Upgrader considers the system as up-to-date 10.540
# 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 3.831
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.413
After features/support/hooks.rb:331 1.081
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
21.018
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.667
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.223
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.058
But a current signing key is available on our website 0.000
When the network is plugged 0.021
And Tor is ready 10.239
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.754
After features/support/hooks.rb:331 0.728
After features/support/hooks.rb:100 0.000