Project Number Date
test_Tails_ISO_devel 4505 21 Jul 2026, 19:49

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 13:2.676 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:17.268
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.069
And I create a 7200 MiB disk named "old" 0.011
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.912
When I start Tails from USB drive "old" with network unplugged 57.950
Then the boot device has safe access rights 3.526
And Tails is running from USB drive "old" 0.262
And there is no persistence partition on USB drive "old" 0.060
And process "udev-watchdog" is running 0.067
And udev-watchdog is monitoring the correct device 0.251
And I unplug USB drive "old" 0.138
After features/support/hooks.rb:339 3.833
After features/support/hooks.rb:108 0.006
Tags: @product
1:35.756
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.049
And I start Tails from USB drive "old" with network unplugged and I login 59.759
Then Tails is running from USB drive "old" 0.264
And I create a persistent partition 25.893
And I take note of which tps features are available 4.794
Then a Tails persistence partition exists on USB drive "old" 0.636
And I shutdown Tails and wait for the computer to power off 4.358
After features/support/hooks.rb:339 0.175
After features/support/hooks.rb:108 0.016
Tags: @product
1:48.744
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.006
Given a computer 0.056
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:10.851
Then Tails is running from USB drive "old" 0.258
And all tps features are active 5.867
When I write some files expected to persist 1.847
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.198
And all persistence configuration files have safe access rights 0.390
And all persistent directories from the old Tails version have safe access rights 2.143
And I take note of which tps features are available 4.986
And I shutdown Tails and wait for the computer to power off 8.512
# 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.631
After features/support/hooks.rb:339 0.647
After features/support/hooks.rb:108 0.008
Tags: @product
2:16.773
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.578
And I log in to a new session 14.939
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.898
And I plug USB drive "to_upgrade" 2.260
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.296
Then the running Tails is installed on USB drive "to_upgrade" 17.501
And I unplug USB drive "to_upgrade" 0.148
And I unplug USB drive "__internal" 0.150
After features/support/hooks.rb:339 2.444
After features/support/hooks.rb:108 0.000
Tags: @product
1:23.112
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.065
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:14.555
Then all tps features from the old Tails version are active 1.341
And Tails is running from USB drive "to_upgrade" 0.342
And the boot device has safe access rights 3.291
And the expected persistent files created with the old Tails version are present in the filesystem 1.383
And all persistent directories from the old Tails version have safe access rights 2.133
After features/support/hooks.rb:339 0.848
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
4:18.679
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.732
And no SquashFS delta is installed 0.087
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.292
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.282
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.419
When the network is plugged 0.016
And Tor is ready 13.179
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.944
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.721
Given I shutdown Tails and wait for the computer to power off 6.947
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.817
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 5.875
And the file system changes introduced in version 6.2~testoverlayfs are present 0.272
And only the 6.2~testoverlayfs SquashFS delta is installed 0.046
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.255
# 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.242
When the network is plugged 0.014
And Tor is ready 11.896
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.458
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.986
Given I shutdown Tails and wait for the computer to power off 4.714
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.194
Then Tails is running version 6.3~testoverlayfs 0.024
And all tps features are active 5.908
And the file system changes introduced in version 6.3~testoverlayfs are present 0.559
And only the 6.3~testoverlayfs SquashFS delta is installed 0.042
# 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.131
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.217
When the network is plugged 0.016
And Tor is ready 16.324
Then the Upgrader considers the system as up-to-date 10.757
# 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.820
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.410
After features/support/hooks.rb:339 0.870
After features/support/hooks.rb:108 0.049
Tags: @product @automatic_upgrade
22.342
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.018
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.269
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
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.019
And Tor is ready 9.787
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.151
After features/support/hooks.rb:339 0.933
After features/support/hooks.rb:108 0.000