Project Number Date
test_Tails_ISO_stable 5964 22 Nov 2025, 12:44

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 16:50.016 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
2:11.564
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.196
And I create a 7200 MiB disk named "old" 0.067
And I plug USB drive "old" 1.071
And I write an old version of the Tails USB image to disk "old" 35.365
When I start Tails from USB drive "old" with network unplugged 1:31.269
Then the boot device has safe access rights 2.797
And Tails is running from USB drive "old" 0.262
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.058
And udev-watchdog is monitoring the correct device 0.238
And I unplug USB drive "old" 0.175
After features/support/hooks.rb:331 3.989
After features/support/hooks.rb:100 0.008
Tags: @product
2:3.969
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.162
And I start Tails from USB drive "old" with network unplugged and I login 1:25.427
Then Tails is running from USB drive "old" 0.326
And I create a persistent partition 28.708
And I take note of which tps features are available 1.112
Then a Tails persistence partition exists on USB drive "old" 0.731
And I shutdown Tails and wait for the computer to power off 7.500
After features/support/hooks.rb:331 0.569
After features/support/hooks.rb:100 0.009
Tags: @product
2:3.673
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.175
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:33.433
Then Tails is running from USB drive "old" 0.317
And all tps features are active 1.819
When I write some files expected to persist 1.592
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.171
And all persistence configuration files have safe access rights 0.303
And all persistent directories from the old Tails version have safe access rights 2.546
And I take note of which tps features are available 0.519
And I shutdown Tails and wait for the computer to power off 4.628
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.165
After features/support/hooks.rb:331 0.338
After features/support/hooks.rb:100 0.008
Tags: @product
2:39.903
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.119
And I log in to a new session 16.355
And I clone USB drive "old" to a new USB drive "to_upgrade" 4.797
And I plug USB drive "to_upgrade" 3.175
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:42.609
Then the running Tails is installed on USB drive "to_upgrade" 20.449
And I unplug USB drive "to_upgrade" 0.203
And I unplug USB drive "__internal" 0.192
After features/support/hooks.rb:331 4.076
After features/support/hooks.rb:100 0.000
Tags: @product
1:47.352
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.212
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:38.568
Then all tps features from the old Tails version are active 1.858
And Tails is running from USB drive "to_upgrade" 0.326
And the boot device has safe access rights 2.856
And the expected persistent files created with the old Tails version are present in the filesystem 1.254
And all persistent directories from the old Tails version have safe access rights 2.275
After features/support/hooks.rb:331 0.587
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
5:39.780
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 28.708
And no SquashFS delta is installed 0.066
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.256
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.268
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.468
When the network is plugged 0.054
And Tor is ready 14.801
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.601
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.749
Given I shutdown Tails and wait for the computer to power off 11.150
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:39.674
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 2.003
And the file system changes introduced in version 6.2~testoverlayfs are present 0.266
And only the 6.2~testoverlayfs SquashFS delta is installed 0.054
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.188
# 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.234
When the network is plugged 0.068
And Tor is ready 41.259
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.660
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.663
Given I shutdown Tails and wait for the computer to power off 7.671
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:36.649
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 2.139
And the file system changes introduced in version 6.3~testoverlayfs are present 0.410
And only the 6.3~testoverlayfs SquashFS delta is installed 0.059
# 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.175
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.242
When the network is plugged 0.189
And Tor is ready 11.027
Then the Upgrader considers the system as up-to-date 0.189
# 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 5.278
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.476
After features/support/hooks.rb:331 1.001
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
23.771
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.074
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.259
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.071
But a current signing key is available on our website 0.000
When the network is plugged 0.058
And Tor is ready 11.610
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.646
After features/support/hooks.rb:331 1.217
After features/support/hooks.rb:100 0.000