Project Number Date
test_Tails_ISO_stable 6146 13 Feb 2026, 12:03

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:31.415 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:21.198
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.164
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.040
And I write an old version of the Tails USB image to disk "old" 27.569
When I start Tails from USB drive "old" with network unplugged 48.706
Then the boot device has safe access rights 2.898
And Tails is running from USB drive "old" 0.261
And there is no persistence partition on USB drive "old" 0.053
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.233
And I unplug USB drive "old" 0.171
After features/support/hooks.rb:331 3.503
After features/support/hooks.rb:100 0.010
Tags: @product
1:38.941
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.170
And I start Tails from USB drive "old" with network unplugged and I login 1:0.268
Then Tails is running from USB drive "old" 0.292
And I create a persistent partition 28.744
And I take note of which tps features are available 1.267
Then a Tails persistence partition exists on USB drive "old" 0.668
And I shutdown Tails and wait for the computer to power off 7.527
After features/support/hooks.rb:331 0.527
After features/support/hooks.rb:100 0.032
Tags: @product
1:42.484
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Given a computer 0.172
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:10.339
Then Tails is running from USB drive "old" 0.303
And all tps features are active 1.776
When I write some files expected to persist 1.415
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.199
And all persistence configuration files have safe access rights 0.332
And all persistent directories from the old Tails version have safe access rights 2.130
And I take note of which tps features are available 0.418
And I shutdown Tails and wait for the computer to power off 7.812
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.585
After features/support/hooks.rb:331 0.463
After features/support/hooks.rb:100 0.010
Tags: @product
2:14.897
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 9.810
And I log in to a new session 8.639
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.272
And I plug USB drive "to_upgrade" 2.698
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.865
Then the running Tails is installed on USB drive "to_upgrade" 18.195
And I unplug USB drive "to_upgrade" 0.237
And I unplug USB drive "__internal" 0.176
After features/support/hooks.rb:331 1.591
After features/support/hooks.rb:100 0.000
Tags: @product
1:19.550
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.162
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:11.383
Then all tps features from the old Tails version are active 1.393
And Tails is running from USB drive "to_upgrade" 0.295
And the boot device has safe access rights 2.819
And the expected persistent files created with the old Tails version are present in the filesystem 1.212
And all persistent directories from the old Tails version have safe access rights 2.283
After features/support/hooks.rb:331 0.831
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
3:54.220
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.411
And no SquashFS delta is installed 0.070
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.197
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.242
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.330
When the network is plugged 0.063
And Tor is ready 13.116
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.571
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.892
Given I shutdown Tails and wait for the computer to power off 7.485
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.737
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 1.930
And the file system changes introduced in version 6.2~testoverlayfs are present 0.275
And only the 6.2~testoverlayfs SquashFS delta is installed 0.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.145
# 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.206
When the network is plugged 0.060
And Tor is ready 11.834
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.738
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.225
Given I shutdown Tails and wait for the computer to power off 7.604
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.226
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 1.923
And the file system changes introduced in version 6.3~testoverlayfs are present 0.432
And only the 6.3~testoverlayfs SquashFS delta is installed 0.055
# 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.140
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.221
When the network is plugged 0.061
And Tor is ready 11.953
Then the Upgrader considers the system as up-to-date 0.147
# 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.290
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.487
After features/support/hooks.rb:331 0.963
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
20.122
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 8.811
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.204
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.076
And the signing key used by the Upgrader is outdated 0.055
But a current signing key is available on our website 0.000
When the network is plugged 0.053
And Tor is ready 10.352
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.569
After features/support/hooks.rb:331 0.834
After features/support/hooks.rb:100 0.000