Project Number Date
test_Tails_ISO_devel 4300 28 Mar 2026, 11:34

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 13:30.248 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:15.252
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.065
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 14.293
When I start Tails from USB drive "old" with network unplugged 56.198
Then the boot device has safe access rights 2.888
And Tails is running from USB drive "old" 0.273
And there is no persistence partition on USB drive "old" 0.048
And process "udev-watchdog" is running 0.078
And udev-watchdog is monitoring the correct device 0.223
And I unplug USB drive "old" 0.159
After features/support/hooks.rb:331 1.523
After features/support/hooks.rb:100 0.007
Tags: @product
1:28.882
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.060
And I start Tails from USB drive "old" with network unplugged and I login 54.836
Then Tails is running from USB drive "old" 0.296
And I create a persistent partition 23.931
And I take note of which tps features are available 0.754
Then a Tails persistence partition exists on USB drive "old" 0.563
And I shutdown Tails and wait for the computer to power off 8.440
After features/support/hooks.rb:331 0.652
After features/support/hooks.rb:100 0.007
Tags: @product
1:30.767
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.073
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.464
Then Tails is running from USB drive "old" 0.323
And all tps features are active 1.212
When I write some files expected to persist 1.773
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.174
And all persistence configuration files have safe access rights 0.471
And all persistent directories from the old Tails version have safe access rights 1.965
And I take note of which tps features are available 0.178
And I shutdown Tails and wait for the computer to power off 8.041
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.089
After features/support/hooks.rb:331 0.601
After features/support/hooks.rb:100 0.006
Tags: @product
2:19.970
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.560
And I log in to a new session 18.678
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.760
And I plug USB drive "to_upgrade" 2.231
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.682
Then the running Tails is installed on USB drive "to_upgrade" 16.772
And I unplug USB drive "to_upgrade" 0.141
And I unplug USB drive "__internal" 0.143
After features/support/hooks.rb:331 2.386
After features/support/hooks.rb:100 0.000
Tags: @product
1:19.929
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.079
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:11.511
Then all tps features from the old Tails version are active 1.305
And Tails is running from USB drive "to_upgrade" 0.312
And the boot device has safe access rights 3.083
And the expected persistent files created with the old Tails version are present in the filesystem 1.495
And all persistent directories from the old Tails version have safe access rights 2.141
After features/support/hooks.rb:331 0.946
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
5:4.242
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 with a persistent partition enabled and logged in 8.594
And no SquashFS delta is installed 0.123
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.285
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.225
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.391
When the network is plugged 0.018
And Tor is ready 41.512
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.403
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.449
Given I shutdown Tails and wait for the computer to power off 20.829
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.934
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.386
And the file system changes introduced in version 6.2~testoverlayfs are present 0.257
And only the 6.2~testoverlayfs SquashFS delta is installed 0.060
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.135
# 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.249
When the network is plugged 0.016
And Tor is ready 21.797
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.551
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.328
Given I shutdown Tails and wait for the computer to power off 17.642
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.223
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.239
And the file system changes introduced in version 6.3~testoverlayfs are present 0.369
And only the 6.3~testoverlayfs SquashFS delta is installed 0.053
# 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.141
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.239
When the network is plugged 0.026
And Tor is ready 21.397
Then the Upgrader considers the system as up-to-date 0.104
# 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.805
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.387
After features/support/hooks.rb:331 0.791
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
31.204
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.761
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.236
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.066
But a current signing key is available on our website 0.000
When the network is plugged 0.019
And Tor is ready 22.669
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.397
After features/support/hooks.rb:331 0.664
After features/support/hooks.rb:100 0.000