Project Number Date
test_Tails_ISO_stable 6548 30 Jul 2026, 11: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:41.583 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:9.997
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.056
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.035
And I write an old version of the Tails USB image to disk "old" 13.698
When I start Tails from USB drive "old" with network unplugged 52.046
Then the boot device has safe access rights 2.519
And Tails is running from USB drive "old" 0.230
And there is no persistence partition on USB drive "old" 0.038
And process "udev-watchdog" is running 0.062
And udev-watchdog is monitoring the correct device 0.171
And I unplug USB drive "old" 0.128
After features/support/hooks.rb:339 1.569
After features/support/hooks.rb:108 0.006
Tags: @product
1:25.472
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.065
And I start Tails from USB drive "old" with network unplugged and I login 52.515
Then Tails is running from USB drive "old" 0.224
And I create a persistent partition 24.049
And I take note of which tps features are available 3.918
Then a Tails persistence partition exists on USB drive "old" 0.586
And I shutdown Tails and wait for the computer to power off 4.112
After features/support/hooks.rb:339 0.391
After features/support/hooks.rb:108 0.006
Tags: @product
1:30.976
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.047
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.024
Then Tails is running from USB drive "old" 0.223
And all tps features are active 4.718
When I write some files expected to persist 1.401
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.202
And all persistence configuration files have safe access rights 0.267
And all persistent directories from the old Tails version have safe access rights 2.041
And I take note of which tps features are available 3.875
And I shutdown Tails and wait for the computer to power off 4.000
# 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.173
After features/support/hooks.rb:339 0.419
After features/support/hooks.rb:108 0.006
Tags: @product
2:9.566
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 7.736
And I log in to a new session 12.368
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.736
And I plug USB drive "to_upgrade" 2.264
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.430
Then the running Tails is installed on USB drive "to_upgrade" 14.748
And I unplug USB drive "to_upgrade" 0.138
And I unplug USB drive "__internal" 0.142
After features/support/hooks.rb:339 2.043
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.419
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.048
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.683
Then all tps features from the old Tails version are active 1.115
And Tails is running from USB drive "to_upgrade" 0.246
And the boot device has safe access rights 2.448
And the expected persistent files created with the old Tails version are present in the filesystem 1.064
And all persistent directories from the old Tails version have safe access rights 1.811
After features/support/hooks.rb:339 0.809
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:54.752
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.022
And no SquashFS delta is installed 0.061
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.216
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.225
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.393
When the network is plugged 0.026
And Tor is ready 12.552
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.833
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.884
Given I shutdown Tails and wait for the computer to power off 6.813
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.376
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.862
And the file system changes introduced in version 6.2~testoverlayfs are present 0.294
And only the 6.2~testoverlayfs SquashFS delta is installed 0.061
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.128
# 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.278
When the network is plugged 0.039
And Tor is ready 14.597
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.787
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.958
Given I shutdown Tails and wait for the computer to power off 4.403
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.926
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.610
And the file system changes introduced in version 6.3~testoverlayfs are present 0.371
And only the 6.3~testoverlayfs SquashFS delta is installed 0.048
# 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.181
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.231
When the network is plugged 0.015
And Tor is ready 10.101
Then the Upgrader considers the system as up-to-date 10.548
# 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.356
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.490
After features/support/hooks.rb:339 0.885
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
20.399
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.298
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.268
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the signing key used by the Upgrader is outdated 0.037
But a current signing key is available on our website 0.000
When the network is plugged 0.024
And Tor is ready 9.896
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.837
After features/support/hooks.rb:339 0.893
After features/support/hooks.rb:108 0.000