Project Number Date
test_Tails_ISO_stable 6680 17 Sep 2026, 15:55

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:45.408 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:5.544
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.140
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 14.469
When I start Tails from USB drive "old" with network unplugged 46.580
Then the boot device has safe access rights 2.393
And Tails is running from USB drive "old" 0.273
And there is no persistence partition on USB drive "old" 0.107
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.296
And I unplug USB drive "old" 0.148
After features/support/hooks.rb:339 1.490
After features/support/hooks.rb:108 0.009
Tags: @product
1:30.029
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.007
Given a computer 0.121
And I start Tails from USB drive "old" with network unplugged and I login 52.703
Then Tails is running from USB drive "old" 0.263
And I create a persistent partition 25.221
And I take note of which tps features are available 6.928
Then a Tails persistence partition exists on USB drive "old" 0.567
And I shutdown Tails and wait for the computer to power off 4.223
After features/support/hooks.rb:339 0.353
After features/support/hooks.rb:108 0.008
Tags: @product
1:37.346
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.093
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.805
Then Tails is running from USB drive "old" 0.211
And all tps features are active 7.170
When I write some files expected to persist 1.234
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.149
And all persistence configuration files have safe access rights 0.335
And all persistent directories from the old Tails version have safe access rights 1.999
And I take note of which tps features are available 5.943
And I shutdown Tails and wait for the computer to power off 3.984
# 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" 12.418
After features/support/hooks.rb:339 0.538
After features/support/hooks.rb:108 0.008
Tags: @product
2:13.770
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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.719
And I log in to a new session 11.684
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.625
And I plug USB drive "to_upgrade" 2.231
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.077
Then the running Tails is installed on USB drive "to_upgrade" 19.176
And I unplug USB drive "to_upgrade" 0.125
And I unplug USB drive "__internal" 0.129
After features/support/hooks.rb:339 2.090
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.204
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.007
Given a computer 0.090
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.667
Then all tps features from the old Tails version are active 1.059
And Tails is running from USB drive "to_upgrade" 0.195
And the boot device has safe access rights 2.252
And the expected persistent files created with the old Tails version are present in the filesystem 1.008
And all persistent directories from the old Tails version have safe access rights 1.930
After features/support/hooks.rb:339 0.494
After features/support/hooks.rb:108 0.007
Tags: @product @automatic_upgrade
3:45.261
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 9.080
And no SquashFS delta is installed 0.061
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.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.178
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.431
When the network is plugged 0.025
And Tor is ready 12.577
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.667
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.575
Given I shutdown Tails and wait for the computer to power off 5.495
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.280
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 9.014
And the file system changes introduced in version 6.2~testoverlayfs are present 0.207
And only the 6.2~testoverlayfs SquashFS delta is installed 0.045
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.123
# 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.209
When the network is plugged 0.025
And Tor is ready 10.796
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.131
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.294
Given I shutdown Tails and wait for the computer to power off 3.978
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.433
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 9.392
And the file system changes introduced in version 6.3~testoverlayfs are present 0.332
And only the 6.3~testoverlayfs SquashFS delta is installed 0.038
# 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.138
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.257
When the network is plugged 0.555
And Tor is ready 10.331
Then the Upgrader considers the system as up-to-date 0.129
# 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 3.780
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.362
After features/support/hooks.rb:339 0.695
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
21.251
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 8.144
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.241
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.050
But a current signing key is available on our website 0.000
When the network is plugged 0.026
And Tor is ready 11.247
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.484
After features/support/hooks.rb:339 1.019
After features/support/hooks.rb:108 0.000