Project Number Date
test_Tails_ISO_stable 6537 28 Jul 2026, 11:50

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:6.669 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:3.330
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.062
And I create a 7200 MiB disk named "old" 0.011
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 13.892
When I start Tails from USB drive "old" with network unplugged 44.894
Then the boot device has safe access rights 2.753
And Tails is running from USB drive "old" 0.233
And there is no persistence partition on USB drive "old" 0.049
And process "udev-watchdog" is running 0.064
And udev-watchdog is monitoring the correct device 0.207
And I unplug USB drive "old" 0.143
After features/support/hooks.rb:339 1.273
After features/support/hooks.rb:108 0.006
Tags: @product
1:30.913
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 55.380
Then Tails is running from USB drive "old" 0.274
And I create a persistent partition 25.408
And I take note of which tps features are available 4.270
Then a Tails persistence partition exists on USB drive "old" 0.552
And I shutdown Tails and wait for the computer to power off 4.974
After features/support/hooks.rb:339 0.490
After features/support/hooks.rb:108 0.007
Tags: @product
1:39.130
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.125
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:7.546
Then Tails is running from USB drive "old" 0.271
And all tps features are active 5.174
When I write some files expected to persist 1.304
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.239
And all persistence configuration files have safe access rights 0.378
And all persistent directories from the old Tails version have safe access rights 2.381
And I take note of which tps features are available 4.405
And I shutdown Tails and wait for the computer to power off 4.257
# 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" 13.046
After features/support/hooks.rb:339 0.338
After features/support/hooks.rb:108 0.006
Tags: @product
2:16.013
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.251
And I log in to a new session 14.791
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.927
And I plug USB drive "to_upgrade" 2.264
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.603
Then the running Tails is installed on USB drive "to_upgrade" 16.778
And I unplug USB drive "to_upgrade" 0.254
And I unplug USB drive "__internal" 0.141
After features/support/hooks.rb:339 2.557
After features/support/hooks.rb:108 0.000
Tags: @product
1:19.735
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 "to_upgrade" with network unplugged and I login with persistence enabled 1:12.074
Then all tps features from the old Tails version are active 1.066
And Tails is running from USB drive "to_upgrade" 0.230
And the boot device has safe access rights 2.584
And the expected persistent files created with the old Tails version are present in the filesystem 1.438
And all persistent directories from the old Tails version have safe access rights 2.274
After features/support/hooks.rb:339 0.626
After features/support/hooks.rb:108 0.027
Tags: @product @automatic_upgrade
3:57.835
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.321
And no SquashFS delta is installed 0.071
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.209
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.263
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.455
When the network is plugged 0.018
And Tor is ready 14.001
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.013
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.222
Given I shutdown Tails and wait for the computer to power off 7.014
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.693
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 5.494
And the file system changes introduced in version 6.2~testoverlayfs are present 0.230
And only the 6.2~testoverlayfs SquashFS delta is installed 0.051
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.146
# 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.222
When the network is plugged 0.013
And Tor is ready 10.132
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.397
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.413
Given I shutdown Tails and wait for the computer to power off 4.096
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.721
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 4.778
And the file system changes introduced in version 6.3~testoverlayfs are present 0.442
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.160
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.257
When the network is plugged 0.015
And Tor is ready 10.208
Then the Upgrader considers the system as up-to-date 10.649
# 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.584
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.405
After features/support/hooks.rb:339 0.787
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
19.710
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.388
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.220
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
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.017
And Tor is ready 10.003
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.986
After features/support/hooks.rb:339 1.061
After features/support/hooks.rb:108 0.000