Project Number Date
test_Tails_ISO_stable 6734 10 Oct 2026, 11:36

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:28.373 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.460
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.099
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.212
When I start Tails from USB drive "old" with network unplugged 53.403
Then the boot device has safe access rights 2.140
And Tails is running from USB drive "old" 0.185
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.053
And udev-watchdog is monitoring the correct device 0.158
And I unplug USB drive "old" 0.121
After features/support/hooks.rb:339 3.549
After features/support/hooks.rb:108 0.006
Tags: @product
1:23.099
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.087
And I start Tails from USB drive "old" with network unplugged and I login 48.033
Then Tails is running from USB drive "old" 0.168
And I create a persistent partition 23.340
And I take note of which tps features are available 6.749
Then a Tails persistence partition exists on USB drive "old" 0.599
And I shutdown Tails and wait for the computer to power off 4.119
After features/support/hooks.rb:339 0.208
After features/support/hooks.rb:108 0.006
Tags: @product
1:30.253
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.086
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.372
Then Tails is running from USB drive "old" 0.178
And all tps features are active 6.888
When I write some files expected to persist 1.327
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.179
And all persistence configuration files have safe access rights 0.309
And all persistent directories from the old Tails version have safe access rights 1.813
And I take note of which tps features are available 6.049
And I shutdown Tails and wait for the computer to power off 2.545
# 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.503
After features/support/hooks.rb:339 0.579
After features/support/hooks.rb:108 0.007
Tags: @product
2:11.897
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.251
And I log in to a new session 11.940
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.800
And I plug USB drive "to_upgrade" 2.234
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.746
Then the running Tails is installed on USB drive "to_upgrade" 17.692
And I unplug USB drive "to_upgrade" 0.121
And I unplug USB drive "__internal" 0.110
After features/support/hooks.rb:339 1.586
After features/support/hooks.rb:108 0.000
Tags: @product
1:8.993
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.109
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.261
Then all tps features from the old Tails version are active 1.506
And Tails is running from USB drive "to_upgrade" 0.191
And the boot device has safe access rights 2.236
And the expected persistent files created with the old Tails version are present in the filesystem 0.913
And all persistent directories from the old Tails version have safe access rights 1.774
After features/support/hooks.rb:339 0.687
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:45.655
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 21.581
And no SquashFS delta is installed 0.058
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.038
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.206
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.244
When the network is plugged 0.035
And Tor is ready 10.747
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.905
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.593
Given I shutdown Tails and wait for the computer to power off 5.271
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.370
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.224
And the file system changes introduced in version 6.2~testoverlayfs are present 0.236
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.078
# 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.226
When the network is plugged 0.034
And Tor is ready 10.302
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.913
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.923
Given I shutdown Tails and wait for the computer to power off 4.028
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.620
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.722
And the file system changes introduced in version 6.3~testoverlayfs are present 0.322
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.101
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.211
When the network is plugged 0.027
And Tor is ready 10.404
Then the Upgrader considers the system as up-to-date 0.110
# 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.495
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.327
After features/support/hooks.rb:339 0.715
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
18.013
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 8.015
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.240
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the signing key used by the Upgrader is outdated 0.037
But a current signing key is available on our website 0.000
When the network is plugged 0.034
And Tor is ready 8.202
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.438
After features/support/hooks.rb:339 0.654
After features/support/hooks.rb:108 0.000