Project Number Date
test_Tails_ISO_stable 6305 16 Apr 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:0.507 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:1.006
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.015
Given a computer 0.093
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 13.669
When I start Tails from USB drive "old" with network unplugged 42.447
Then the boot device has safe access rights 2.973
And Tails is running from USB drive "old" 0.309
And there is no persistence partition on USB drive "old" 0.056
And process "udev-watchdog" is running 0.058
And udev-watchdog is monitoring the correct device 0.208
And I unplug USB drive "old" 0.157
After features/support/hooks.rb:331 1.241
After features/support/hooks.rb:100 0.007
Tags: @product
1:24.095
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.057
And I start Tails from USB drive "old" with network unplugged and I login 54.641
Then Tails is running from USB drive "old" 0.286
And I create a persistent partition 23.786
And I take note of which tps features are available 0.727
Then a Tails persistence partition exists on USB drive "old" 0.561
And I shutdown Tails and wait for the computer to power off 4.034
After features/support/hooks.rb:331 0.334
After features/support/hooks.rb:100 0.010
Tags: @product
1:32.790
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.078
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.984
Then Tails is running from USB drive "old" 0.299
And all tps features are active 1.534
When I write some files expected to persist 1.576
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.315
And all persistence configuration files have safe access rights 0.613
And all persistent directories from the old Tails version have safe access rights 2.166
And I take note of which tps features are available 0.151
And I shutdown Tails and wait for the computer to power off 8.037
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.034
After features/support/hooks.rb:331 0.587
After features/support/hooks.rb:100 0.012
Tags: @product
2:11.838
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 without a persistent partition and stopped at Tails Greeter's login screen 8.054
And I log in to a new session 12.995
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.751
And I plug USB drive "to_upgrade" 2.225
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.896
Then the running Tails is installed on USB drive "to_upgrade" 15.354
And I unplug USB drive "to_upgrade" 0.199
And I unplug USB drive "__internal" 0.360
After features/support/hooks.rb:331 2.572
After features/support/hooks.rb:100 0.000
Tags: @product
1:12.223
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.066
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.398
Then all tps features from the old Tails version are active 1.056
And Tails is running from USB drive "to_upgrade" 0.239
And the boot device has safe access rights 2.321
And the expected persistent files created with the old Tails version are present in the filesystem 1.263
And all persistent directories from the old Tails version have safe access rights 1.877
After features/support/hooks.rb:331 0.545
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
4:50.594
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.379
And no SquashFS delta is installed 0.095
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.230
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.252
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.392
When the network is plugged 0.043
And Tor is ready 21.871
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.402
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.367
Given I shutdown Tails and wait for the computer to power off 20.219
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.411
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.331
And the file system changes introduced in version 6.2~testoverlayfs are present 0.277
And only the 6.2~testoverlayfs SquashFS delta is installed 0.048
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.164
# 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.241
When the network is plugged 0.015
And Tor is ready 20.767
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.375
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.260
Given I shutdown Tails and wait for the computer to power off 17.534
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.469
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.065
And the file system changes introduced in version 6.3~testoverlayfs are present 0.448
And only the 6.3~testoverlayfs SquashFS delta is installed 0.093
# 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.158
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.273
When the network is plugged 0.016
And Tor is ready 40.895
Then the Upgrader considers the system as up-to-date 0.095
# 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.955
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.378
After features/support/hooks.rb:331 0.943
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
47.958
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 with a persistent partition enabled and logged in 7.752
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.260
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the signing key used by the Upgrader is outdated 0.049
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 39.370
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.450
After features/support/hooks.rb:331 0.840
After features/support/hooks.rb:100 0.000