Project Number Date
test_Tails_ISO_devel 4235 17 Feb 2026, 12:00

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 12:2.301 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:26.645
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.054
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 14.187
When I start Tails from USB drive "old" with network unplugged 1:8.066
Then the boot device has safe access rights 2.619
And Tails is running from USB drive "old" 0.242
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.198
And I unplug USB drive "old" 0.127
After features/support/hooks.rb:331 1.292
After features/support/hooks.rb:100 0.006
Tags: @product
1:25.689
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.064
And I start Tails from USB drive "old" with network unplugged and I login 53.836
Then Tails is running from USB drive "old" 0.287
And I create a persistent partition 24.328
And I take note of which tps features are available 0.904
Then a Tails persistence partition exists on USB drive "old" 0.661
And I shutdown Tails and wait for the computer to power off 5.606
After features/support/hooks.rb:331 0.183
After features/support/hooks.rb:100 0.006
Tags: @product
1:26.708
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.054
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.943
Then Tails is running from USB drive "old" 0.268
And all tps features are active 1.099
When I write some files expected to persist 1.412
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.159
And all persistence configuration files have safe access rights 0.294
And all persistent directories from the old Tails version have safe access rights 1.891
And I take note of which tps features are available 0.152
And I shutdown Tails and wait for the computer to power off 8.012
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.419
After features/support/hooks.rb:331 0.181
After features/support/hooks.rb:100 0.006
Tags: @product
2:17.235
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.197
And I log in to a new session 12.179
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.808
And I plug USB drive "to_upgrade" 2.285
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.218
Then the running Tails is installed on USB drive "to_upgrade" 17.258
And I unplug USB drive "to_upgrade" 0.140
And I unplug USB drive "__internal" 0.146
After features/support/hooks.rb:331 1.657
After features/support/hooks.rb:100 0.000
Tags: @product
1:14.021
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.058
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.059
Then all tps features from the old Tails version are active 1.087
And Tails is running from USB drive "to_upgrade" 0.256
And the boot device has safe access rights 2.593
And the expected persistent files created with the old Tails version are present in the filesystem 1.157
And all persistent directories from the old Tails version have safe access rights 1.807
After features/support/hooks.rb:331 0.738
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
3:52.752
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.991
And no SquashFS delta is installed 0.076
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.235
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.213
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.340
When the network is plugged 0.018
And Tor is ready 13.799
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.693
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.677
Given I shutdown Tails and wait for the computer to power off 12.707
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.855
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.247
And the file system changes introduced in version 6.2~testoverlayfs are present 0.282
And only the 6.2~testoverlayfs SquashFS delta is installed 0.041
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.171
# 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.222
When the network is plugged 0.024
And Tor is ready 11.397
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.428
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.355
Given I shutdown Tails and wait for the computer to power off 8.386
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.366
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.156
And the file system changes introduced in version 6.3~testoverlayfs are present 0.399
And only the 6.3~testoverlayfs SquashFS delta is installed 0.060
# 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.143
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.206
When the network is plugged 0.016
And Tor is ready 10.041
Then the Upgrader considers the system as up-to-date 10.479
# 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.182
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.450
After features/support/hooks.rb:331 0.980
After features/support/hooks.rb:100 0.033
Tags: @product @automatic_upgrade
19.249
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.614
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.249
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the signing key used by the Upgrader is outdated 0.045
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 10.852
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.429
After features/support/hooks.rb:331 1.006
After features/support/hooks.rb:100 0.000