Project Number Date
test_Tails_ISO_stable 6254 01 Apr 2026, 11:22

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:46.734 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:29.909
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.068
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 15.096
When I start Tails from USB drive "old" with network unplugged 1:9.207
Then the boot device has safe access rights 3.569
And Tails is running from USB drive "old" 0.371
And there is no persistence partition on USB drive "old" 0.118
And process "udev-watchdog" is running 0.066
And udev-watchdog is monitoring the correct device 0.230
And I unplug USB drive "old" 0.150
After features/support/hooks.rb:331 1.942
After features/support/hooks.rb:100 0.009
Tags: @product
1:34.419
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.111
And I start Tails from USB drive "old" with network unplugged and I login 59.020
Then Tails is running from USB drive "old" 0.348
And I create a persistent partition 26.413
And I take note of which tps features are available 0.862
Then a Tails persistence partition exists on USB drive "old" 0.621
And I shutdown Tails and wait for the computer to power off 7.042
After features/support/hooks.rb:331 0.472
After features/support/hooks.rb:100 0.015
Tags: @product
1:33.326
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.083
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.497
Then Tails is running from USB drive "old" 0.294
And all tps features are active 1.117
When I write some files expected to persist 1.382
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.182
And all persistence configuration files have safe access rights 0.454
And all persistent directories from the old Tails version have safe access rights 1.904
And I take note of which tps features are available 0.149
And I shutdown Tails and wait for the computer to power off 8.281
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.977
After features/support/hooks.rb:331 0.521
After features/support/hooks.rb:100 0.006
Tags: @product
2:19.645
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.977
And I log in to a new session 15.255
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.219
And I plug USB drive "to_upgrade" 2.327
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.701
Then the running Tails is installed on USB drive "to_upgrade" 17.845
And I unplug USB drive "to_upgrade" 0.163
And I unplug USB drive "__internal" 0.155
After features/support/hooks.rb:331 2.374
After features/support/hooks.rb:100 0.000
Tags: @product
1:20.121
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.057
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:12.233
Then all tps features from the old Tails version are active 1.115
And Tails is running from USB drive "to_upgrade" 0.285
And the boot device has safe access rights 2.960
And the expected persistent files created with the old Tails version are present in the filesystem 1.283
And all persistent directories from the old Tails version have safe access rights 2.185
After features/support/hooks.rb:331 0.698
After features/support/hooks.rb:100 0.010
4:59.528
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.789
And no SquashFS delta is installed 0.075
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.240
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.418
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.421
When the network is plugged 0.027
And Tor is ready 23.023
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.386
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.787
Given I shutdown Tails and wait for the computer to power off 20.046
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:20.505
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.329
And the file system changes introduced in version 6.2~testoverlayfs are present 0.381
And only the 6.2~testoverlayfs SquashFS delta is installed 0.036
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.159
# 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.250
When the network is plugged 0.026
And Tor is ready 20.560
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.525
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.015
Given I shutdown Tails and wait for the computer to power off 17.816
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:21.442
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.557
And the file system changes introduced in version 6.3~testoverlayfs are present 0.408
And only the 6.3~testoverlayfs SquashFS delta is installed 0.051
# 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.225
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.257
When the network is plugged 0.024
And Tor is ready 22.589
Then the Upgrader considers the system as up-to-date 0.114
# 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.535
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.429
After features/support/hooks.rb:331 1.225
After features/support/hooks.rb:100 0.056
29.783
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.565
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.250
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the signing key used by the Upgrader is outdated 0.068
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 20.373
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.461
After features/support/hooks.rb:331 1.010
After features/support/hooks.rb:100 0.000