Project Number Date
test_Tails_ISO_stable 6278 08 Apr 2026, 18:17

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:35.643 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:25.248
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.055
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 15.099
When I start Tails from USB drive "old" with network unplugged 1:5.272
Then the boot device has safe access rights 2.954
And Tails is running from USB drive "old" 0.322
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.070
And udev-watchdog is monitoring the correct device 0.227
And I unplug USB drive "old" 0.162
After features/support/hooks.rb:331 1.658
After features/support/hooks.rb:100 0.008
Tags: @product
1:35.331
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.082
And I start Tails from USB drive "old" with network unplugged and I login 1:1.442
Then Tails is running from USB drive "old" 0.282
And I create a persistent partition 24.577
And I take note of which tps features are available 0.940
Then a Tails persistence partition exists on USB drive "old" 0.819
And I shutdown Tails and wait for the computer to power off 7.185
After features/support/hooks.rb:331 0.550
After features/support/hooks.rb:100 0.008
Tags: @product
1:31.072
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.076
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.668
Then Tails is running from USB drive "old" 0.408
And all tps features are active 1.237
When I write some files expected to persist 1.511
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.214
And all persistence configuration files have safe access rights 0.601
And all persistent directories from the old Tails version have safe access rights 2.377
And I take note of which tps features are available 0.266
And I shutdown Tails and wait for the computer to power off 4.316
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.394
After features/support/hooks.rb:331 0.241
After features/support/hooks.rb:100 0.011
Tags: @product
2:18.502
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 8.016
And I log in to a new session 16.427
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.923
And I plug USB drive "to_upgrade" 2.238
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.484
Then the running Tails is installed on USB drive "to_upgrade" 18.068
And I unplug USB drive "to_upgrade" 0.160
And I unplug USB drive "__internal" 0.182
After features/support/hooks.rb:331 3.412
After features/support/hooks.rb:100 0.000
Tags: @product
1:16.721
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.084
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.301
Then all tps features from the old Tails version are active 1.305
And Tails is running from USB drive "to_upgrade" 0.245
And the boot device has safe access rights 3.023
And the expected persistent files created with the old Tails version are present in the filesystem 1.497
And all persistent directories from the old Tails version have safe access rights 2.264
After features/support/hooks.rb:331 0.647
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
4:59.841
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 9.282
And no SquashFS delta is installed 0.133
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.298
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.282
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.410
When the network is plugged 0.016
And Tor is ready 26.294
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.441
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.519
Given I shutdown Tails and wait for the computer to power off 20.904
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:21.754
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.239
And the file system changes introduced in version 6.2~testoverlayfs are present 0.269
And only the 6.2~testoverlayfs SquashFS delta is installed 0.055
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.175
# 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.244
When the network is plugged 0.016
And Tor is ready 20.986
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.379
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.567
Given I shutdown Tails and wait for the computer to power off 17.464
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.227
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.227
And the file system changes introduced in version 6.3~testoverlayfs are present 0.477
And only the 6.3~testoverlayfs SquashFS delta is installed 0.052
# 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.146
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.220
When the network is plugged 0.018
And Tor is ready 23.332
Then the Upgrader considers the system as up-to-date 0.168
# 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.557
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.608
After features/support/hooks.rb:331 0.862
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
28.925
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.117
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.264
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
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.019
And Tor is ready 20.051
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.379
After features/support/hooks.rb:331 0.835
After features/support/hooks.rb:100 0.000