Project Number Date
test_Tails_ISO_devel 4576 29 Aug 2026, 10:58

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:51.392 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
59.834
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.090
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.001
When I start Tails from USB drive "old" with network unplugged 43.262
Then the boot device has safe access rights 1.846
And Tails is running from USB drive "old" 0.227
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.048
And udev-watchdog is monitoring the correct device 0.158
And I unplug USB drive "old" 0.118
After features/support/hooks.rb:339 1.721
After features/support/hooks.rb:108 0.005
Tags: @product
1:19.039
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.080
And I start Tails from USB drive "old" with network unplugged and I login 46.856
Then Tails is running from USB drive "old" 0.206
And I create a persistent partition 22.754
And I take note of which tps features are available 5.972
Then a Tails persistence partition exists on USB drive "old" 0.503
And I shutdown Tails and wait for the computer to power off 2.665
After features/support/hooks.rb:339 0.271
After features/support/hooks.rb:108 0.005
Tags: @product
1:27.037
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.082
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.828
Then Tails is running from USB drive "old" 0.198
And all tps features are active 6.558
When I write some files expected to persist 0.974
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.157
And all persistence configuration files have safe access rights 0.202
And all persistent directories from the old Tails version have safe access rights 1.402
And I take note of which tps features are available 6.018
And I shutdown Tails and wait for the computer to power off 2.569
# 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.044
After features/support/hooks.rb:339 0.253
After features/support/hooks.rb:108 0.005
Tags: @product
2:9.625
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.290
And I log in to a new session 10.135
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.559
And I plug USB drive "to_upgrade" 2.302
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.546
Then the running Tails is installed on USB drive "to_upgrade" 17.535
And I unplug USB drive "to_upgrade" 0.130
And I unplug USB drive "__internal" 0.125
After features/support/hooks.rb:339 1.719
After features/support/hooks.rb:108 0.000
Tags: @product
1:3.712
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.078
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.507
Then all tps features from the old Tails version are active 0.920
And Tails is running from USB drive "to_upgrade" 0.232
And the boot device has safe access rights 1.824
And the expected persistent files created with the old Tails version are present in the filesystem 0.743
And all persistent directories from the old Tails version have safe access rights 1.406
After features/support/hooks.rb:339 0.488
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:34.641
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 20.894
And no SquashFS delta is installed 0.073
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.218
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.024
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.218
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.294
When the network is plugged 0.024
And Tor is ready 11.682
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.973
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.625
Given I shutdown Tails and wait for the computer to power off 5.474
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.462
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 7.380
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.037
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.082
# 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.023
And Tor is ready 9.674
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.534
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.062
Given I shutdown Tails and wait for the computer to power off 2.691
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.074
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.206
And the file system changes introduced in version 6.3~testoverlayfs are present 0.346
And only the 6.3~testoverlayfs SquashFS delta is installed 0.038
# 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.090
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.154
When the network is plugged 0.022
And Tor is ready 10.369
Then the Upgrader considers the system as up-to-date 0.098
# 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.134
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.324
After features/support/hooks.rb:339 0.601
After features/support/hooks.rb:108 0.008
Tags: @product @automatic_upgrade
17.502
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.563
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.190
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
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.029
And Tor is ready 8.130
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.480
After features/support/hooks.rb:339 0.615
After features/support/hooks.rb:108 0.000