Project Number Date
test_Tails_ISO_stable 6226 24 Mar 2026, 11:25

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:56.251 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.475
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.062
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 14.356
When I start Tails from USB drive "old" with network unplugged 1:1.650
Then the boot device has safe access rights 3.532
And Tails is running from USB drive "old" 0.279
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.065
And udev-watchdog is monitoring the correct device 0.264
And I unplug USB drive "old" 0.172
After features/support/hooks.rb:331 3.695
After features/support/hooks.rb:100 0.014
Tags: @product
1:32.280
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.091
And I start Tails from USB drive "old" with network unplugged and I login 1:0.141
Then Tails is running from USB drive "old" 0.251
And I create a persistent partition 26.140
And I take note of which tps features are available 0.898
Then a Tails persistence partition exists on USB drive "old" 0.591
And I shutdown Tails and wait for the computer to power off 4.165
After features/support/hooks.rb:331 0.607
After features/support/hooks.rb:100 0.008
Tags: @product
1:27.551
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.091
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.715
Then Tails is running from USB drive "old" 0.285
And all tps features are active 1.252
When I write some files expected to persist 1.462
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.192
And all persistence configuration files have safe access rights 0.521
And all persistent directories from the old Tails version have safe access rights 2.124
And I take note of which tps features are available 0.166
And I shutdown Tails and wait for the computer to power off 4.139
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.597
After features/support/hooks.rb:331 0.297
After features/support/hooks.rb:100 0.006
Tags: @product
2:28.344
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.857
And I log in to a new session 22.145
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.927
And I plug USB drive "to_upgrade" 2.251
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.761
Then the running Tails is installed on USB drive "to_upgrade" 18.069
And I unplug USB drive "to_upgrade" 0.164
And I unplug USB drive "__internal" 0.166
After features/support/hooks.rb:331 1.036
After features/support/hooks.rb:100 0.000
Tags: @product
1:13.867
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.097
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.628
Then all tps features from the old Tails version are active 1.044
And Tails is running from USB drive "to_upgrade" 0.245
And the boot device has safe access rights 2.653
And the expected persistent files created with the old Tails version are present in the filesystem 1.140
And all persistent directories from the old Tails version have safe access rights 2.057
After features/support/hooks.rb:331 1.084
After features/support/hooks.rb:100 0.084
5:24.281
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.831
And no SquashFS delta is installed 0.071
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.242
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.305
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.374
When the network is plugged 0.027
And Tor is ready 30.021
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.443
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.152
Given I shutdown Tails and wait for the computer to power off 21.081
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:19.073
Then Tails is running version 6.2~testoverlayfs 0.009
And all tps features are active 1.225
And the file system changes introduced in version 6.2~testoverlayfs are present 0.286
And only the 6.2~testoverlayfs SquashFS delta is installed 0.084
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.197
# 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.220
When the network is plugged 0.016
And Tor is ready 40.277
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.417
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.402
Given I shutdown Tails and wait for the computer to power off 18.104
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:20.288
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.231
And the file system changes introduced in version 6.3~testoverlayfs are present 0.416
And only the 6.3~testoverlayfs SquashFS delta is installed 0.041
# 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.156
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.200
When the network is plugged 0.022
And Tor is ready 22.344
Then the Upgrader considers the system as up-to-date 0.115
# 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.064
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.460
After features/support/hooks.rb:331 1.037
After features/support/hooks.rb:100 0.034
28.450
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 8.402
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.217
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
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.018
And Tor is ready 19.313
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.397
After features/support/hooks.rb:331 1.144
After features/support/hooks.rb:100 0.000