Project Number Date
test_Tails_ISO_stable 6237 26 Mar 2026, 11:33

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 13:22.859 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:38.644
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.053
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 14.178
When I start Tails from USB drive "old" with network unplugged 1:19.556
Then the boot device has safe access rights 3.033
And Tails is running from USB drive "old" 0.345
And there is no persistence partition on USB drive "old" 0.055
And process "udev-watchdog" is running 0.067
And udev-watchdog is monitoring the correct device 0.192
And I unplug USB drive "old" 0.136
After features/support/hooks.rb:331 3.545
After features/support/hooks.rb:100 0.006
Tags: @product
1:28.324
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.050
And I start Tails from USB drive "old" with network unplugged and I login 56.975
Then Tails is running from USB drive "old" 0.277
And I create a persistent partition 24.909
And I take note of which tps features are available 0.817
Then a Tails persistence partition exists on USB drive "old" 0.621
And I shutdown Tails and wait for the computer to power off 4.671
After features/support/hooks.rb:331 0.220
After features/support/hooks.rb:100 0.009
Tags: @product
1:26.817
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.065
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.549
Then Tails is running from USB drive "old" 0.321
And all tps features are active 1.246
When I write some files expected to persist 1.405
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.178
And all persistence configuration files have safe access rights 0.395
And all persistent directories from the old Tails version have safe access rights 2.250
And I take note of which tps features are available 0.154
And I shutdown Tails and wait for the computer to power off 3.999
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.250
After features/support/hooks.rb:331 0.514
After features/support/hooks.rb:100 0.007
Tags: @product
2:23.562
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.300
And I log in to a new session 20.979
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.862
And I plug USB drive "to_upgrade" 2.292
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.710
Then the running Tails is installed on USB drive "to_upgrade" 17.103
And I unplug USB drive "to_upgrade" 0.153
And I unplug USB drive "__internal" 0.159
After features/support/hooks.rb:331 2.577
After features/support/hooks.rb:100 0.000
Tags: @product
1:12.404
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.056
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.281
Then all tps features from the old Tails version are active 1.214
And Tails is running from USB drive "to_upgrade" 0.344
And the boot device has safe access rights 2.837
And the expected persistent files created with the old Tails version are present in the filesystem 1.240
And all persistent directories from the old Tails version have safe access rights 2.430
After features/support/hooks.rb:331 0.842
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
4:45.057
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.344
And no SquashFS delta is installed 0.078
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.335
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.262
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.399
When the network is plugged 0.022
And Tor is ready 43.935
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.395
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.789
Given I shutdown Tails and wait for the computer to power off 15.704
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.856
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.085
And the file system changes introduced in version 6.2~testoverlayfs are present 0.252
And only the 6.2~testoverlayfs SquashFS delta is installed 0.051
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.160
# 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.199
When the network is plugged 0.022
And Tor is ready 20.687
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.380
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.477
Given I shutdown Tails and wait for the computer to power off 12.324
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.198
Then Tails is running version 6.3~testoverlayfs 0.009
And all tps features are active 1.219
And the file system changes introduced in version 6.3~testoverlayfs are present 0.397
And only the 6.3~testoverlayfs SquashFS delta is installed 0.038
# 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.159
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.193
When the network is plugged 0.014
And Tor is ready 21.625
Then the Upgrader considers the system as up-to-date 0.105
# 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.828
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.439
After features/support/hooks.rb:331 1.035
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
28.048
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.977
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.259
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.041
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 19.298
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.392
After features/support/hooks.rb:331 0.945
After features/support/hooks.rb:100 0.000