Project Number Date
test_Tails_ISO_devel 4218 08 Feb 2026, 11:43

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:30.549 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:3.789
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.060
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 14.210
When I start Tails from USB drive "old" with network unplugged 45.016
Then the boot device has safe access rights 2.734
And Tails is running from USB drive "old" 0.268
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.064
And udev-watchdog is monitoring the correct device 0.222
And I unplug USB drive "old" 0.143
After features/support/hooks.rb:331 3.871
After features/support/hooks.rb:100 0.018
Tags: @product
1:29.566
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.058
And I start Tails from USB drive "old" with network unplugged and I login 55.220
Then Tails is running from USB drive "old" 0.266
And I create a persistent partition 25.323
And I take note of which tps features are available 0.763
Then a Tails persistence partition exists on USB drive "old" 0.913
And I shutdown Tails and wait for the computer to power off 7.019
After features/support/hooks.rb:331 0.305
After features/support/hooks.rb:100 0.007
Tags: @product
1:28.900
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.063
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.347
Then Tails is running from USB drive "old" 0.249
And all tps features are active 1.081
When I write some files expected to persist 1.201
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.167
And all persistence configuration files have safe access rights 0.286
And all persistent directories from the old Tails version have safe access rights 1.955
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.068
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.325
After features/support/hooks.rb:331 0.460
After features/support/hooks.rb:100 0.007
Tags: @product
2:12.977
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.339
And I log in to a new session 10.025
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.857
And I plug USB drive "to_upgrade" 2.271
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.030
Then the running Tails is installed on USB drive "to_upgrade" 17.160
And I unplug USB drive "to_upgrade" 0.153
And I unplug USB drive "__internal" 0.139
After features/support/hooks.rb:331 2.031
After features/support/hooks.rb:100 0.000
Tags: @product
1:11.828
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.068
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.910
Then all tps features from the old Tails version are active 1.208
And Tails is running from USB drive "to_upgrade" 0.282
And the boot device has safe access rights 2.763
And the expected persistent files created with the old Tails version are present in the filesystem 1.270
And all persistent directories from the old Tails version have safe access rights 2.324
After features/support/hooks.rb:331 1.019
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
3:44.187
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.735
And no SquashFS delta is installed 0.076
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.220
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.227
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.343
When the network is plugged 0.016
And Tor is ready 12.746
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.765
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.065
Given I shutdown Tails and wait for the computer to power off 9.639
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.097
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.105
And the file system changes introduced in version 6.2~testoverlayfs are present 0.194
And only the 6.2~testoverlayfs SquashFS delta is installed 0.097
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.146
# 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.214
When the network is plugged 0.018
And Tor is ready 11.330
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.767
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.464
Given I shutdown Tails and wait for the computer to power off 7.979
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.829
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.229
And the file system changes introduced in version 6.3~testoverlayfs are present 0.405
And only the 6.3~testoverlayfs SquashFS delta is installed 0.046
# 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.121
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.198
When the network is plugged 0.015
And Tor is ready 9.715
Then the Upgrader considers the system as up-to-date 10.623
# 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.292
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.393
After features/support/hooks.rb:331 0.727
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
19.299
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.462
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.369
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
And the signing key used by the Upgrader is outdated 0.051
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 9.512
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.851
After features/support/hooks.rb:331 0.980
After features/support/hooks.rb:100 0.000