Project Number Date
test_Tails_ISO_stable 6150 17 Feb 2026, 12:45

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 15:38.267 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.230
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.195
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.042
And I write an old version of the Tails USB image to disk "old" 31.403
When I start Tails from USB drive "old" with network unplugged 1:5.111
Then the boot device has safe access rights 3.518
And Tails is running from USB drive "old" 0.344
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.060
And udev-watchdog is monitoring the correct device 0.253
And I unplug USB drive "old" 0.185
After features/support/hooks.rb:331 1.538
After features/support/hooks.rb:100 0.008
Tags: @product
1:50.450
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.162
And I start Tails from USB drive "old" with network unplugged and I login 1:9.700
Then Tails is running from USB drive "old" 0.353
And I create a persistent partition 30.414
And I take note of which tps features are available 1.284
Then a Tails persistence partition exists on USB drive "old" 0.712
And I shutdown Tails and wait for the computer to power off 7.823
After features/support/hooks.rb:331 0.884
After features/support/hooks.rb:100 0.010
Tags: @product
1:56.463
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:20.902
Then Tails is running from USB drive "old" 0.760
And all tps features are active 2.247
When I write some files expected to persist 1.662
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.304
And all persistence configuration files have safe access rights 0.445
And all persistent directories from the old Tails version have safe access rights 2.507
And I take note of which tps features are available 0.467
And I shutdown Tails and wait for the computer to power off 7.885
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.085
After features/support/hooks.rb:331 0.485
After features/support/hooks.rb:100 0.012
Tags: @product
3:16.523
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 31.276
And I log in to a new session 15.042
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.878
And I plug USB drive "to_upgrade" 2.689
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:58.365
Then the running Tails is installed on USB drive "to_upgrade" 26.824
And I unplug USB drive "to_upgrade" 0.219
And I unplug USB drive "__internal" 0.227
After features/support/hooks.rb:331 2.814
After features/support/hooks.rb:100 0.000
Tags: @product
1:28.461
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.190
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:19.242
Then all tps features from the old Tails version are active 1.408
And Tails is running from USB drive "to_upgrade" 0.274
And the boot device has safe access rights 3.275
And the expected persistent files created with the old Tails version are present in the filesystem 1.596
And all persistent directories from the old Tails version have safe access rights 2.472
After features/support/hooks.rb:331 1.765
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
4:59.472
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 21.088
And no SquashFS delta is installed 0.153
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.254
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.315
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.461
When the network is plugged 2.861
And Tor is ready 18.931
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.759
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 15.900
Given I shutdown Tails and wait for the computer to power off 12.774
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:29.597
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.656
And the file system changes introduced in version 6.2~testoverlayfs are present 0.320
And only the 6.2~testoverlayfs SquashFS delta is installed 0.063
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.173
# 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.277
When the network is plugged 0.097
And Tor is ready 11.188
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.152
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.727
Given I shutdown Tails and wait for the computer to power off 4.928
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:21.090
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 2.590
And the file system changes introduced in version 6.3~testoverlayfs are present 0.539
And only the 6.3~testoverlayfs SquashFS delta is installed 0.060
# 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.155
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.229
When the network is plugged 0.053
And Tor is ready 13.303
Then the Upgrader considers the system as up-to-date 0.202
# 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.980
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.507
After features/support/hooks.rb:331 0.868
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
24.666
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.641
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.317
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 0.067
But a current signing key is available on our website 0.000
When the network is plugged 0.053
And Tor is ready 11.918
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.606
After features/support/hooks.rb:331 0.942
After features/support/hooks.rb:100 0.000