Project Number Date
test_Tails_ISO_devel 4598 06 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 11:8.430 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
57.637
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.082
And I create a 7200 MiB disk named "old" 0.018
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.742
When I start Tails from USB drive "old" with network unplugged 40.058
Then the boot device has safe access rights 2.094
And Tails is running from USB drive "old" 0.227
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.056
And udev-watchdog is monitoring the correct device 0.179
And I unplug USB drive "old" 0.116
After features/support/hooks.rb:339 3.465
After features/support/hooks.rb:108 0.007
Tags: @product
1:22.565
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 "old" with network unplugged and I login 47.590
Then Tails is running from USB drive "old" 0.192
And I create a persistent partition 24.957
And I take note of which tps features are available 6.600
Then a Tails persistence partition exists on USB drive "old" 0.487
And I shutdown Tails and wait for the computer to power off 2.654
After features/support/hooks.rb:339 0.264
After features/support/hooks.rb:108 0.005
Tags: @product
1:34.040
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.088
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.116
Then Tails is running from USB drive "old" 0.226
And all tps features are active 6.934
When I write some files expected to persist 1.297
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.141
And all persistence configuration files have safe access rights 0.337
And all persistent directories from the old Tails version have safe access rights 1.560
And I take note of which tps features are available 6.614
And I shutdown Tails and wait for the computer to power off 4.094
# 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.628
After features/support/hooks.rb:339 0.232
After features/support/hooks.rb:108 0.005
Tags: @product
2:11.817
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 9.516
And I log in to a new session 11.268
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.758
And I plug USB drive "to_upgrade" 2.224
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.310
Then the running Tails is installed on USB drive "to_upgrade" 17.496
And I unplug USB drive "to_upgrade" 0.128
And I unplug USB drive "__internal" 0.114
After features/support/hooks.rb:339 1.708
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.712
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.084
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.463
Then all tps features from the old Tails version are active 1.201
And Tails is running from USB drive "to_upgrade" 0.241
And the boot device has safe access rights 2.597
And the expected persistent files created with the old Tails version are present in the filesystem 1.165
And all persistent directories from the old Tails version have safe access rights 1.958
After features/support/hooks.rb:339 0.974
After features/support/hooks.rb:108 0.034
Tags: @product @automatic_upgrade
3:32.240
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.299
And no SquashFS delta is installed 0.180
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.206
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.240
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.374
When the network is plugged 0.028
And Tor is ready 11.375
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.047
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.641
Given I shutdown Tails and wait for the computer to power off 7.080
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.289
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.218
And the file system changes introduced in version 6.2~testoverlayfs are present 0.220
And only the 6.2~testoverlayfs SquashFS delta is installed 0.033
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.103
# 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.198
When the network is plugged 0.025
And Tor is ready 10.520
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.580
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.725
Given I shutdown Tails and wait for the computer to power off 2.624
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.334
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 7.838
And the file system changes introduced in version 6.3~testoverlayfs are present 0.299
And only the 6.3~testoverlayfs SquashFS delta is installed 0.058
# 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.114
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.225
When the network is plugged 0.036
And Tor is ready 10.363
Then the Upgrader considers the system as up-to-date 0.071
# 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.518
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.314
After features/support/hooks.rb:339 0.743
After features/support/hooks.rb:108 0.013
Tags: @product @automatic_upgrade
18.417
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.966
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.215
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 0.047
But a current signing key is available on our website 0.000
When the network is plugged 0.027
And Tor is ready 8.641
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.467
After features/support/hooks.rb:339 0.783
After features/support/hooks.rb:108 0.000