Project Number Date
test_Tails_ISO_devel 4503 21 Jul 2026, 11:30

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 11:40.989 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:15.999
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.050
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 13.167
When I start Tails from USB drive "old" with network unplugged 58.260
Then the boot device has safe access rights 2.848
And Tails is running from USB drive "old" 0.191
And there is no persistence partition on USB drive "old" 0.048
And process "udev-watchdog" is running 0.065
And udev-watchdog is monitoring the correct device 0.205
And I unplug USB drive "old" 0.139
After features/support/hooks.rb:339 1.459
After features/support/hooks.rb:108 0.006
Tags: @product
1:29.877
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.045
And I start Tails from USB drive "old" with network unplugged and I login 52.074
Then Tails is running from USB drive "old" 0.236
And I create a persistent partition 24.989
And I take note of which tps features are available 3.960
Then a Tails persistence partition exists on USB drive "old" 0.484
And I shutdown Tails and wait for the computer to power off 8.086
After features/support/hooks.rb:339 0.510
After features/support/hooks.rb:108 0.005
Tags: @product
1:31.661
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.044
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.955
Then Tails is running from USB drive "old" 0.253
And all tps features are active 4.639
When I write some files expected to persist 1.245
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.215
And all persistence configuration files have safe access rights 0.276
And all persistent directories from the old Tails version have safe access rights 1.884
And I take note of which tps features are available 3.606
And I shutdown Tails and wait for the computer to power off 2.662
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 11.877
After features/support/hooks.rb:339 0.160
After features/support/hooks.rb:108 0.006
Tags: @product
2:9.239
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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 7.921
And I log in to a new session 12.479
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.815
And I plug USB drive "to_upgrade" 2.226
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.399
Then the running Tails is installed on USB drive "to_upgrade" 14.110
And I unplug USB drive "to_upgrade" 0.140
And I unplug USB drive "__internal" 0.146
After features/support/hooks.rb:339 2.157
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.217
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.049
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.336
Then all tps features from the old Tails version are active 1.060
And Tails is running from USB drive "to_upgrade" 0.220
And the boot device has safe access rights 2.417
And the expected persistent files created with the old Tails version are present in the filesystem 1.164
And all persistent directories from the old Tails version have safe access rights 1.968
After features/support/hooks.rb:339 0.545
After features/support/hooks.rb:108 0.007
Tags: @product @automatic_upgrade
3:42.159
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.667
And no SquashFS delta is installed 0.057
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.212
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.197
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.308
When the network is plugged 0.013
And Tor is ready 13.164
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.983
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.338
Given I shutdown Tails and wait for the computer to power off 6.860
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.298
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 4.885
And the file system changes introduced in version 6.2~testoverlayfs are present 0.210
And only the 6.2~testoverlayfs SquashFS delta is installed 0.040
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.131
# 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.222
When the network is plugged 0.017
And Tor is ready 9.752
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.108
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.627
Given I shutdown Tails and wait for the computer to power off 4.010
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.625
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.954
And the file system changes introduced in version 6.3~testoverlayfs are present 0.326
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.175
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.226
When the network is plugged 0.014
And Tor is ready 9.530
Then the Upgrader considers the system as up-to-date 10.561
# 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.169
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.333
After features/support/hooks.rb:339 0.792
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
20.835
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.402
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.261
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.057
But a current signing key is available on our website 0.000
When the network is plugged 0.019
And Tor is ready 10.140
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.898
After features/support/hooks.rb:339 0.866
After features/support/hooks.rb:108 0.000