Project Number Date
test_Tails_ISO_stable 6639 04 Sep 2026, 11:21

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 10:42.610 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
55.683
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.084
And I create a 7200 MiB disk named "old" 0.018
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.437
When I start Tails from USB drive "old" with network unplugged 38.782
Then the boot device has safe access rights 1.861
And Tails is running from USB drive "old" 0.162
And there is no persistence partition on USB drive "old" 0.038
And process "udev-watchdog" is running 0.058
And udev-watchdog is monitoring the correct device 0.112
And I unplug USB drive "old" 0.107
After features/support/hooks.rb:339 3.384
After features/support/hooks.rb:108 0.038
Tags: @product
1:16.750
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.087
And I start Tails from USB drive "old" with network unplugged and I login 45.894
Then Tails is running from USB drive "old" 0.175
And I create a persistent partition 21.492
And I take note of which tps features are available 6.071
Then a Tails persistence partition exists on USB drive "old" 0.475
And I shutdown Tails and wait for the computer to power off 2.552
After features/support/hooks.rb:339 0.591
After features/support/hooks.rb:108 0.005
Tags: @product
1:27.665
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.083
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.262
Then Tails is running from USB drive "old" 0.214
And all tps features are active 6.632
When I write some files expected to persist 1.087
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.158
And all persistence configuration files have safe access rights 0.314
And all persistent directories from the old Tails version have safe access rights 1.585
And I take note of which tps features are available 5.712
And I shutdown Tails and wait for the computer to power off 2.524
# 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.090
After features/support/hooks.rb:339 0.135
After features/support/hooks.rb:108 0.005
Tags: @product
2:8.368
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 7.915
And I log in to a new session 10.268
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.753
And I plug USB drive "to_upgrade" 2.203
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.325
Then the running Tails is installed on USB drive "to_upgrade" 16.670
And I unplug USB drive "to_upgrade" 0.128
And I unplug USB drive "__internal" 0.102
After features/support/hooks.rb:339 1.508
After features/support/hooks.rb:108 0.000
Tags: @product
1:3.610
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.083
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.304
Then all tps features from the old Tails version are active 0.860
And Tails is running from USB drive "to_upgrade" 0.166
And the boot device has safe access rights 1.867
And the expected persistent files created with the old Tails version are present in the filesystem 0.810
And all persistent directories from the old Tails version have safe access rights 1.517
After features/support/hooks.rb:339 0.553
After features/support/hooks.rb:108 0.061
Tags: @product @automatic_upgrade
3:32.421
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.247
And no SquashFS delta is installed 0.064
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.038
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.189
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.304
When the network is plugged 0.034
And Tor is ready 13.106
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.843
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.805
Given I shutdown Tails and wait for the computer to power off 5.215
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.585
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.688
And the file system changes introduced in version 6.2~testoverlayfs are present 0.167
And only the 6.2~testoverlayfs SquashFS delta is installed 0.050
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.087
# 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.148
When the network is plugged 0.036
And Tor is ready 10.026
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.311
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.542
Given I shutdown Tails and wait for the computer to power off 2.676
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.499
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.746
And the file system changes introduced in version 6.3~testoverlayfs are present 0.309
And only the 6.3~testoverlayfs SquashFS delta is installed 0.036
# 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.097
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.185
When the network is plugged 0.031
And Tor is ready 10.276
Then the Upgrader considers the system as up-to-date 10.460
# 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.055
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.319
After features/support/hooks.rb:339 0.898
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
18.110
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.627
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.031
And the signing key used by the Upgrader is outdated 0.042
But a current signing key is available on our website 0.000
When the network is plugged 0.032
And Tor is ready 9.303
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.852
After features/support/hooks.rb:339 0.532
After features/support/hooks.rb:108 0.000