Project Number Date
test_Tails_ISO_fix-bad-comments 2 01 Jul 2026, 17:53

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:17.698 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:16.058
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.053
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.682
When I start Tails from USB drive "old" with network unplugged 57.710
Then the boot device has safe access rights 2.857
And Tails is running from USB drive "old" 0.275
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.219
And I unplug USB drive "old" 0.133
After features/support/hooks.rb:339 1.673
After features/support/hooks.rb:108 0.006
Tags: @product
1:33.231
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.046
And I start Tails from USB drive "old" with network unplugged and I login 55.583
Then Tails is running from USB drive "old" 0.246
And I create a persistent partition 23.911
And I take note of which tps features are available 4.684
Then a Tails persistence partition exists on USB drive "old" 0.534
And I shutdown Tails and wait for the computer to power off 8.224
After features/support/hooks.rb:339 0.272
After features/support/hooks.rb:108 0.006
Tags: @product
1:39.177
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.067
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.555
Then Tails is running from USB drive "old" 0.290
And all tps features are active 5.238
When I write some files expected to persist 1.316
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.143
And all persistence configuration files have safe access rights 0.269
And all persistent directories from the old Tails version have safe access rights 1.857
And I take note of which tps features are available 4.006
And I shutdown Tails and wait for the computer to power off 8.100
# 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.331
After features/support/hooks.rb:339 0.176
After features/support/hooks.rb:108 0.006
Tags: @product
2:12.009
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.262
And I log in to a new session 12.750
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.830
And I plug USB drive "to_upgrade" 2.271
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.326
Then the running Tails is installed on USB drive "to_upgrade" 16.297
And I unplug USB drive "to_upgrade" 0.135
And I unplug USB drive "__internal" 0.135
After features/support/hooks.rb:339 2.076
After features/support/hooks.rb:108 0.000
Tags: @product
1:13.571
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.051
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.878
Then all tps features from the old Tails version are active 1.349
And Tails is running from USB drive "to_upgrade" 0.256
And the boot device has safe access rights 2.661
And the expected persistent files created with the old Tails version are present in the filesystem 1.325
And all persistent directories from the old Tails version have safe access rights 2.049
After features/support/hooks.rb:339 0.772
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
4:2.229
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.250
And no SquashFS delta is installed 0.076
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.251
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.266
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.437
When the network is plugged 0.025
And Tor is ready 13.829
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.404
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.474
Given I shutdown Tails and wait for the computer to power off 11.443
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.169
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 5.455
And the file system changes introduced in version 6.2~testoverlayfs are present 0.268
And only the 6.2~testoverlayfs SquashFS delta is installed 0.043
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.144
# 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.232
When the network is plugged 0.039
And Tor is ready 10.061
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.191
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.923
Given I shutdown Tails and wait for the computer to power off 8.127
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.290
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 5.529
And the file system changes introduced in version 6.3~testoverlayfs are present 0.375
And only the 6.3~testoverlayfs SquashFS delta is installed 0.050
# 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.177
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.237
When the network is plugged 0.014
And Tor is ready 10.093
Then the Upgrader considers the system as up-to-date 10.559
# 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.312
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.393
After features/support/hooks.rb:339 0.777
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
21.420
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.348
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.069
And the signing key used by the Upgrader is outdated 0.051
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 10.550
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.141
After features/support/hooks.rb:339 0.777
After features/support/hooks.rb:108 0.000