Project Number Date
test_Tails_ISO_devel 4252 24 Feb 2026, 23: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 15:58.042 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:31.139
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.223
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.040
And I write an old version of the Tails USB image to disk "old" 28.761
When I start Tails from USB drive "old" with network unplugged 56.640
Then the boot device has safe access rights 3.558
And Tails is running from USB drive "old" 0.322
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.066
And udev-watchdog is monitoring the correct device 0.236
And I unplug USB drive "old" 0.178
After features/support/hooks.rb:331 3.720
After features/support/hooks.rb:100 0.009
Tags: @product
1:56.239
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.248
And I start Tails from USB drive "old" with network unplugged and I login 1:10.413
Then Tails is running from USB drive "old" 0.603
And I create a persistent partition 33.429
And I take note of which tps features are available 3.098
Then a Tails persistence partition exists on USB drive "old" 0.665
And I shutdown Tails and wait for the computer to power off 7.779
After features/support/hooks.rb:331 0.372
After features/support/hooks.rb:100 0.010
Tags: @product
2:5.275
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.252
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:28.800
Then Tails is running from USB drive "old" 0.627
And all tps features are active 2.054
When I write some files expected to persist 1.481
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.208
And all persistence configuration files have safe access rights 0.356
And all persistent directories from the old Tails version have safe access rights 2.317
And I take note of which tps features are available 0.549
And I shutdown Tails and wait for the computer to power off 8.168
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 20.458
After features/support/hooks.rb:331 0.260
After features/support/hooks.rb:100 0.012
Tags: @product
2:30.586
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.013
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.638
And I log in to a new session 11.815
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.617
And I plug USB drive "to_upgrade" 2.762
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.966
Then the running Tails is installed on USB drive "to_upgrade" 22.395
And I unplug USB drive "to_upgrade" 0.194
And I unplug USB drive "__internal" 0.196
After features/support/hooks.rb:331 2.087
After features/support/hooks.rb:100 0.000
Tags: @product
1:36.344
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.187
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:25.487
Then all tps features from the old Tails version are active 2.131
And Tails is running from USB drive "to_upgrade" 0.405
And the boot device has safe access rights 3.635
And the expected persistent files created with the old Tails version are present in the filesystem 1.656
And all persistent directories from the old Tails version have safe access rights 2.839
After features/support/hooks.rb:331 0.649
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
5:45.413
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 10.455
And no SquashFS delta is installed 0.093
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.281
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.102
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.299
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.434
When the network is plugged 0.099
And Tor is ready 21.104
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.642
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.588
Given I shutdown Tails and wait for the computer to power off 17.792
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:38.763
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.424
And the file system changes introduced in version 6.2~testoverlayfs are present 0.330
And only the 6.2~testoverlayfs SquashFS delta is installed 0.059
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.160
# 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.268
When the network is plugged 0.053
And Tor is ready 25.135
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.817
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.596
Given I shutdown Tails and wait for the computer to power off 18.096
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:38.705
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.695
And the file system changes introduced in version 6.3~testoverlayfs are present 0.541
And only the 6.3~testoverlayfs SquashFS delta is installed 0.077
# 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.182
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.316
When the network is plugged 0.057
And Tor is ready 23.959
Then the Upgrader considers the system as up-to-date 0.134
# 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 6.135
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.978
After features/support/hooks.rb:331 1.281
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
33.043
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 10.756
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.250
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the signing key used by the Upgrader is outdated 0.064
But a current signing key is available on our website 0.000
When the network is plugged 0.049
And Tor is ready 21.217
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.632
After features/support/hooks.rb:331 1.403
After features/support/hooks.rb:100 0.000