Project Number Date
test_Tails_ISO_stable 6617 31 Aug 2026, 18:40

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:37.268 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.229
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.085
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 14.052
When I start Tails from USB drive "old" with network unplugged 43.976
Then the boot device has safe access rights 2.377
And Tails is running from USB drive "old" 0.283
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.051
And udev-watchdog is monitoring the correct device 0.192
And I unplug USB drive "old" 0.127
After features/support/hooks.rb:339 3.850
After features/support/hooks.rb:108 0.026
Tags: @product
1:26.353
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.095
And I start Tails from USB drive "old" with network unplugged and I login 50.999
Then Tails is running from USB drive "old" 0.257
And I create a persistent partition 23.958
And I take note of which tps features are available 6.270
Then a Tails persistence partition exists on USB drive "old" 0.544
And I shutdown Tails and wait for the computer to power off 4.228
After features/support/hooks.rb:339 0.509
After features/support/hooks.rb:108 0.005
Tags: @product
1:39.753
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.109
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.623
Then Tails is running from USB drive "old" 0.209
And all tps features are active 7.516
When I write some files expected to persist 1.212
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.134
And all persistence configuration files have safe access rights 0.290
And all persistent directories from the old Tails version have safe access rights 1.762
And I take note of which tps features are available 7.207
And I shutdown Tails and wait for the computer to power off 4.270
# 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.415
After features/support/hooks.rb:339 0.148
After features/support/hooks.rb:108 0.006
Tags: @product
2:15.915
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 without a persistent partition and stopped at Tails Greeter's login screen 8.851
And I log in to a new session 13.235
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.851
And I plug USB drive "to_upgrade" 2.202
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.023
Then the running Tails is installed on USB drive "to_upgrade" 18.517
And I unplug USB drive "to_upgrade" 0.121
And I unplug USB drive "__internal" 0.111
After features/support/hooks.rb:339 3.896
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.951
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.113
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.233
Then all tps features from the old Tails version are active 1.263
And Tails is running from USB drive "to_upgrade" 0.239
And the boot device has safe access rights 2.358
And the expected persistent files created with the old Tails version are present in the filesystem 1.162
And all persistent directories from the old Tails version have safe access rights 1.580
After features/support/hooks.rb:339 0.792
After features/support/hooks.rb:108 0.007
Tags: @product @automatic_upgrade
3:43.562
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 with a persistent partition enabled and logged in 8.277
And no SquashFS delta is installed 0.064
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.196
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.030
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.294
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.376
When the network is plugged 0.039
And Tor is ready 11.782
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.134
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.514
Given I shutdown Tails and wait for the computer to power off 5.608
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.146
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.903
And the file system changes introduced in version 6.2~testoverlayfs are present 0.234
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.137
# 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.200
When the network is plugged 0.034
And Tor is ready 9.601
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.367
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.558
Given I shutdown Tails and wait for the computer to power off 2.677
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.400
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 8.530
And the file system changes introduced in version 6.3~testoverlayfs are present 0.349
And only the 6.3~testoverlayfs SquashFS delta is installed 0.044
# 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.104
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.198
When the network is plugged 0.028
And Tor is ready 10.649
Then the Upgrader considers the system as up-to-date 10.417
# 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.205
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.373
After features/support/hooks.rb:339 0.786
After features/support/hooks.rb:108 0.021
Tags: @product @automatic_upgrade
19.502
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.249
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.225
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the signing key used by the Upgrader is outdated 0.059
But a current signing key is available on our website 0.000
When the network is plugged 0.028
And Tor is ready 8.657
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.231
After features/support/hooks.rb:339 0.694
After features/support/hooks.rb:108 0.000