Project Number Date
test_Tails_ISO_stable 6543 29 Jul 2026, 11:35

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:35.364 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.760
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.101
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 12.996
When I start Tails from USB drive "old" with network unplugged 58.490
Then the boot device has safe access rights 2.448
And Tails is running from USB drive "old" 0.223
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.061
And udev-watchdog is monitoring the correct device 0.221
And I unplug USB drive "old" 0.130
After features/support/hooks.rb:339 1.318
After features/support/hooks.rb:108 0.006
Tags: @product
1:26.916
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.043
And I start Tails from USB drive "old" with network unplugged and I login 53.820
Then Tails is running from USB drive "old" 0.238
And I create a persistent partition 24.233
And I take note of which tps features are available 3.783
Then a Tails persistence partition exists on USB drive "old" 0.599
And I shutdown Tails and wait for the computer to power off 4.196
After features/support/hooks.rb:339 0.511
After features/support/hooks.rb:108 0.007
Tags: @product
1:30.156
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.705
Then Tails is running from USB drive "old" 0.230
And all tps features are active 4.530
When I write some files expected to persist 1.192
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.145
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.890
And I take note of which tps features are available 3.582
And I shutdown Tails and wait for the computer to power off 3.989
# 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.561
After features/support/hooks.rb:339 0.204
After features/support/hooks.rb:108 0.006
Tags: @product
2:9.266
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.734
And I log in to a new session 12.731
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.698
And I plug USB drive "to_upgrade" 2.223
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.226
Then the running Tails is installed on USB drive "to_upgrade" 14.381
And I unplug USB drive "to_upgrade" 0.130
And I unplug USB drive "__internal" 0.139
After features/support/hooks.rb:339 2.099
After features/support/hooks.rb:108 0.000
Tags: @product
1:8.988
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.052
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.655
Then all tps features from the old Tails version are active 0.927
And Tails is running from USB drive "to_upgrade" 0.248
And the boot device has safe access rights 2.373
And the expected persistent files created with the old Tails version are present in the filesystem 1.010
And all persistent directories from the old Tails version have safe access rights 1.720
After features/support/hooks.rb:339 0.681
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:43.555
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.920
And no SquashFS delta is installed 0.082
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.207
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.216
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.396
When the network is plugged 0.041
And Tor is ready 13.796
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.540
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.706
Given I shutdown Tails and wait for the computer to power off 6.994
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.617
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 5.038
And the file system changes introduced in version 6.2~testoverlayfs are present 0.218
And only the 6.2~testoverlayfs SquashFS delta is installed 0.047
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.170
# 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.214
When the network is plugged 0.016
And Tor is ready 9.908
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.681
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.115
Given I shutdown Tails and wait for the computer to power off 4.118
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.334
Then Tails is running version 6.3~testoverlayfs 0.025
And all tps features are active 4.316
And the file system changes introduced in version 6.3~testoverlayfs are present 0.334
And only the 6.3~testoverlayfs SquashFS delta is installed 0.040
# 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.131
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.189
When the network is plugged 0.014
And Tor is ready 10.463
Then the Upgrader considers the system as up-to-date 10.519
# 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.761
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.329
After features/support/hooks.rb:339 0.976
After features/support/hooks.rb:108 0.058
Tags: @product @automatic_upgrade
20.721
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 7.217
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.198
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
And the signing key used by the Upgrader is outdated 0.039
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 10.522
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.689
After features/support/hooks.rb:339 1.079
After features/support/hooks.rb:108 0.000