Project Number Date
test_Tails_ISO_stable 6504 14 Jul 2026, 11:51

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 12:13.921 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:10.791
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.061
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.960
When I start Tails from USB drive "old" with network unplugged 52.174
Then the boot device has safe access rights 2.891
And Tails is running from USB drive "old" 0.237
And there is no persistence partition on USB drive "old" 0.056
And process "udev-watchdog" is running 0.036
And udev-watchdog is monitoring the correct device 0.198
And I unplug USB drive "old" 0.151
After features/support/hooks.rb:339 3.794
After features/support/hooks.rb:108 0.006
Tags: @product
1:32.401
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.064
And I start Tails from USB drive "old" with network unplugged and I login 54.552
Then Tails is running from USB drive "old" 0.235
And I create a persistent partition 24.734
And I take note of which tps features are available 3.843
Then a Tails persistence partition exists on USB drive "old" 0.555
And I shutdown Tails and wait for the computer to power off 8.415
After features/support/hooks.rb:339 0.477
After features/support/hooks.rb:108 0.007
Tags: @product
1:42.236
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.054
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:7.319
Then Tails is running from USB drive "old" 0.260
And all tps features are active 5.048
When I write some files expected to persist 1.475
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.232
And all persistence configuration files have safe access rights 0.347
And all persistent directories from the old Tails version have safe access rights 2.216
And I take note of which tps features are available 4.559
And I shutdown Tails and wait for the computer to power off 8.267
# 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.454
After features/support/hooks.rb:339 0.141
After features/support/hooks.rb:108 0.006
Tags: @product
2:10.217
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 8.040
And I log in to a new session 12.519
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.886
And I plug USB drive "to_upgrade" 2.207
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.145
Then the running Tails is installed on USB drive "to_upgrade" 15.135
And I unplug USB drive "to_upgrade" 0.149
And I unplug USB drive "__internal" 0.132
After features/support/hooks.rb:339 0.765
After features/support/hooks.rb:108 0.000
Tags: @product
1:16.248
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.053
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.719
Then all tps features from the old Tails version are active 1.170
And Tails is running from USB drive "to_upgrade" 0.261
And the boot device has safe access rights 2.876
And the expected persistent files created with the old Tails version are present in the filesystem 1.243
And all persistent directories from the old Tails version have safe access rights 1.922
After features/support/hooks.rb:339 1.011
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
4:1.827
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 8.440
And no SquashFS delta is installed 0.073
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.341
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.261
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.336
When the network is plugged 0.024
And Tor is ready 13.323
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.901
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.886
Given I shutdown Tails and wait for the computer to power off 11.397
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.090
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.903
And the file system changes introduced in version 6.2~testoverlayfs are present 0.231
And only the 6.2~testoverlayfs SquashFS delta is installed 0.059
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.207
# 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.211
When the network is plugged 0.014
And Tor is ready 10.361
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.732
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.510
Given I shutdown Tails and wait for the computer to power off 7.942
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.349
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 5.061
And the file system changes introduced in version 6.3~testoverlayfs are present 0.395
And only the 6.3~testoverlayfs SquashFS delta is installed 0.042
# 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.144
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.183
When the network is plugged 0.015
And Tor is ready 10.243
Then the Upgrader considers the system as up-to-date 10.530
# 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.208
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.323
After features/support/hooks.rb:339 0.787
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
20.199
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.250
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.257
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.075
And the signing key used by the Upgrader is outdated 0.046
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 10.068
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.485
After features/support/hooks.rb:339 1.056
After features/support/hooks.rb:108 0.000