Project Number Date
test_Tails_ISO_devel 4628 18 Sep 2026, 11:10

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:6.282 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:10.444
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.077
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" 12.989
When I start Tails from USB drive "old" with network unplugged 53.966
Then the boot device has safe access rights 1.832
And Tails is running from USB drive "old" 0.144
And there is no persistence partition on USB drive "old" 0.051
And process "udev-watchdog" is running 0.034
And udev-watchdog is monitoring the correct device 0.148
And I unplug USB drive "old" 0.162
After features/support/hooks.rb:339 3.603
After features/support/hooks.rb:108 0.005
Tags: @product
1:19.708
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.071
And I start Tails from USB drive "old" with network unplugged and I login 47.677
Then Tails is running from USB drive "old" 0.216
And I create a persistent partition 22.581
And I take note of which tps features are available 5.903
Then a Tails persistence partition exists on USB drive "old" 0.548
And I shutdown Tails and wait for the computer to power off 2.707
After features/support/hooks.rb:339 0.608
After features/support/hooks.rb:108 0.006
Tags: @product
1:30.456
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.125
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.590
Then Tails is running from USB drive "old" 0.189
And all tps features are active 7.009
When I write some files expected to persist 0.900
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.125
And all persistence configuration files have safe access rights 0.252
And all persistent directories from the old Tails version have safe access rights 1.463
And I take note of which tps features are available 5.671
And I shutdown Tails and wait for the computer to power off 5.056
# 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.070
After features/support/hooks.rb:339 0.352
After features/support/hooks.rb:108 0.005
Tags: @product
2:9.518
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 8.207
And I log in to a new session 10.955
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.612
And I plug USB drive "to_upgrade" 2.283
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.186
Then the running Tails is installed on USB drive "to_upgrade" 17.054
And I unplug USB drive "to_upgrade" 0.103
And I unplug USB drive "__internal" 0.115
After features/support/hooks.rb:339 1.686
After features/support/hooks.rb:108 0.000
Tags: @product
1:6.070
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.077
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.573
Then all tps features from the old Tails version are active 1.003
And Tails is running from USB drive "to_upgrade" 0.178
And the boot device has safe access rights 2.020
And the expected persistent files created with the old Tails version are present in the filesystem 0.800
And all persistent directories from the old Tails version have safe access rights 1.416
After features/support/hooks.rb:339 0.576
After features/support/hooks.rb:108 0.005
3:30.452
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.807
And no SquashFS delta is installed 0.049
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.160
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.035
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.183
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.324
When the network is plugged 0.036
And Tor is ready 12.634
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.827
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.671
Given I shutdown Tails and wait for the computer to power off 5.320
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.024
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 7.292
And the file system changes introduced in version 6.2~testoverlayfs are present 0.196
And only the 6.2~testoverlayfs SquashFS delta is installed 0.037
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.091
# 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.164
When the network is plugged 0.043
And Tor is ready 10.231
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.859
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.968
Given I shutdown Tails and wait for the computer to power off 2.534
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.088
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 6.808
And the file system changes introduced in version 6.3~testoverlayfs are present 0.283
And only the 6.3~testoverlayfs SquashFS delta is installed 0.030
# 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.087
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.165
When the network is plugged 0.034
And Tor is ready 10.234
Then the Upgrader considers the system as up-to-date 10.381
# 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.505
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.323
After features/support/hooks.rb:339 0.841
After features/support/hooks.rb:108 0.036
19.632
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.943
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.147
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.045
But a current signing key is available on our website 0.000
When the network is plugged 0.025
And Tor is ready 9.330
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.087
After features/support/hooks.rb:339 0.537
After features/support/hooks.rb:108 0.000