Project Number Date
test_Tails_ISO_stable 5946 12 Nov 2025, 12:48

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 16:6.354 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:57.917
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.196
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 31.425
When I start Tails from USB drive "old" with network unplugged 1:21.362
Then the boot device has safe access rights 2.974
And Tails is running from USB drive "old" 0.301
And there is no persistence partition on USB drive "old" 0.057
And process "udev-watchdog" is running 0.068
And udev-watchdog is monitoring the correct device 0.239
And I unplug USB drive "old" 0.194
After features/support/hooks.rb:331 3.866
After features/support/hooks.rb:100 0.026
Tags: @product
2:4.368
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 "old" with network unplugged and I login 1:25.379
Then Tails is running from USB drive "old" 0.335
And I create a persistent partition 28.632
And I take note of which tps features are available 1.366
Then a Tails persistence partition exists on USB drive "old" 0.754
And I shutdown Tails and wait for the computer to power off 7.736
After features/support/hooks.rb:331 0.651
After features/support/hooks.rb:100 0.009
Tags: @product
2:10.446
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:36.387
Then Tails is running from USB drive "old" 0.284
And all tps features are active 1.782
When I write some files expected to persist 1.404
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.198
And all persistence configuration files have safe access rights 0.455
And all persistent directories from the old Tails version have safe access rights 2.318
And I take note of which tps features are available 0.448
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" 19.166
After features/support/hooks.rb:331 0.544
After features/support/hooks.rb:100 0.010
Tags: @product
2:40.066
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 12.802
And I log in to a new session 17.389
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.344
And I plug USB drive "to_upgrade" 2.615
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:44.076
Then the running Tails is installed on USB drive "to_upgrade" 21.413
And I unplug USB drive "to_upgrade" 0.202
And I unplug USB drive "__internal" 0.221
After features/support/hooks.rb:331 3.948
After features/support/hooks.rb:100 0.000
Tags: @product
1:46.606
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.173
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:37.795
Then all tps features from the old Tails version are active 1.622
And Tails is running from USB drive "to_upgrade" 0.319
And the boot device has safe access rights 2.928
And the expected persistent files created with the old Tails version are present in the filesystem 1.402
And all persistent directories from the old Tails version have safe access rights 2.364
After features/support/hooks.rb:331 0.864
After features/support/hooks.rb:100 0.010
5:0.784
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 13.789
And no SquashFS delta is installed 0.088
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.289
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.274
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.392
When the network is plugged 0.054
And Tor is ready 14.089
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.909
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.545
Given I shutdown Tails and wait for the computer to power off 11.361
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:41.138
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.517
And the file system changes introduced in version 6.2~testoverlayfs are present 0.284
And only the 6.2~testoverlayfs SquashFS delta is installed 0.064
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.172
# 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.248
When the network is plugged 0.059
And Tor is ready 12.029
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.931
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.197
Given I shutdown Tails and wait for the computer to power off 7.559
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:39.356
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.540
And the file system changes introduced in version 6.3~testoverlayfs are present 0.435
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.182
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.245
When the network is plugged 0.068
And Tor is ready 10.946
Then the Upgrader considers the system as up-to-date 0.285
# 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.171
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.398
After features/support/hooks.rb:331 0.976
After features/support/hooks.rb:100 0.018
26.165
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 12.205
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.278
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.082
But a current signing key is available on our website 0.000
When the network is plugged 0.070
And Tor is ready 11.638
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.838
After features/support/hooks.rb:331 0.863
After features/support/hooks.rb:100 0.000