Project Number Date
test_Tails_ISO_stable 6328 28 Apr 2026, 11:34

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 12:45.619 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:2.778
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.062
And I create a 7200 MiB disk named "old" 0.011
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 14.299
When I start Tails from USB drive "old" with network unplugged 44.036
Then the boot device has safe access rights 2.660
And Tails is running from USB drive "old" 0.235
And there is no persistence partition on USB drive "old" 0.049
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.197
And I unplug USB drive "old" 0.154
After features/support/hooks.rb:331 3.797
After features/support/hooks.rb:100 0.010
Tags: @product
1:33.160
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.075
And I start Tails from USB drive "old" with network unplugged and I login 56.089
Then Tails is running from USB drive "old" 0.278
And I create a persistent partition 26.711
And I take note of which tps features are available 0.986
Then a Tails persistence partition exists on USB drive "old" 0.563
And I shutdown Tails and wait for the computer to power off 8.455
After features/support/hooks.rb:331 0.245
After features/support/hooks.rb:100 0.007
Tags: @product
1:34.494
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.059
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.742
Then Tails is running from USB drive "old" 0.307
And all tps features are active 1.259
When I write some files expected to persist 1.963
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.207
And all persistence configuration files have safe access rights 0.472
And all persistent directories from the old Tails version have safe access rights 2.638
And I take note of which tps features are available 0.186
And I shutdown Tails and wait for the computer to power off 8.439
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.218
After features/support/hooks.rb:331 0.462
After features/support/hooks.rb:100 0.007
Tags: @product
2:14.355
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 without a persistent partition and stopped at Tails Greeter's login screen 8.353
And I log in to a new session 14.156
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.097
And I plug USB drive "to_upgrade" 2.249
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.938
Then the running Tails is installed on USB drive "to_upgrade" 16.272
And I unplug USB drive "to_upgrade" 0.156
And I unplug USB drive "__internal" 0.131
After features/support/hooks.rb:331 2.272
After features/support/hooks.rb:100 0.000
Tags: @product
1:13.367
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.071
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.289
Then all tps features from the old Tails version are active 1.044
And Tails is running from USB drive "to_upgrade" 0.242
And the boot device has safe access rights 2.487
And the expected persistent files created with the old Tails version are present in the filesystem 1.241
And all persistent directories from the old Tails version have safe access rights 1.990
After features/support/hooks.rb:331 0.907
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
4:39.185
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 9.067
And no SquashFS delta is installed 0.066
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.239
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.264
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.345
When the network is plugged 0.015
And Tor is ready 23.640
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.385
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.633
Given I shutdown Tails and wait for the computer to power off 20.429
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.045
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 1.324
And the file system changes introduced in version 6.2~testoverlayfs are present 0.281
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.161
# 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.190
When the network is plugged 0.056
And Tor is ready 21.356
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.363
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.075
Given I shutdown Tails and wait for the computer to power off 12.476
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.310
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.243
And the file system changes introduced in version 6.3~testoverlayfs are present 0.436
And only the 6.3~testoverlayfs SquashFS delta is installed 0.049
# 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.133
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.228
When the network is plugged 0.018
And Tor is ready 22.374
Then the Upgrader considers the system as up-to-date 0.093
# 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.360
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.387
After features/support/hooks.rb:331 0.944
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
28.277
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 8.299
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.244
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the signing key used by the Upgrader is outdated 0.084
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 19.113
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.452
After features/support/hooks.rb:331 1.237
After features/support/hooks.rb:100 0.000