Project Number Date
test_Tails_ISO_stable 6184 04 Mar 2026, 12:02

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:36.761 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:50.630
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.052
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 14.043
When I start Tails from USB drive "old" with network unplugged 1:31.625
Then the boot device has safe access rights 2.977
And Tails is running from USB drive "old" 0.409
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.112
And udev-watchdog is monitoring the correct device 0.189
And I unplug USB drive "old" 0.135
After features/support/hooks.rb:331 3.617
After features/support/hooks.rb:100 0.029
Tags: @product
1:29.925
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.053
And I start Tails from USB drive "old" with network unplugged and I login 55.885
Then Tails is running from USB drive "old" 0.314
And I create a persistent partition 24.404
And I take note of which tps features are available 0.689
Then a Tails persistence partition exists on USB drive "old" 0.529
And I shutdown Tails and wait for the computer to power off 8.047
After features/support/hooks.rb:331 0.502
After features/support/hooks.rb:100 0.008
Tags: @product
1:29.442
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.071
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.110
Then Tails is running from USB drive "old" 0.283
And all tps features are active 1.134
When I write some files expected to persist 1.507
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.166
And all persistence configuration files have safe access rights 0.435
And all persistent directories from the old Tails version have safe access rights 1.839
And I take note of which tps features are available 0.152
And I shutdown Tails and wait for the computer to power off 7.908
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.834
After features/support/hooks.rb:331 0.391
After features/support/hooks.rb:100 0.008
Tags: @product
2:23.989
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 8.584
And I log in to a new session 13.242
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.946
And I plug USB drive "to_upgrade" 2.267
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:42.199
Then the running Tails is installed on USB drive "to_upgrade" 16.443
And I unplug USB drive "to_upgrade" 0.151
And I unplug USB drive "__internal" 0.154
After features/support/hooks.rb:331 3.288
After features/support/hooks.rb:100 0.000
Tags: @product
1:10.962
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.101
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.818
Then all tps features from the old Tails version are active 0.970
And Tails is running from USB drive "to_upgrade" 0.237
And the boot device has safe access rights 2.711
And the expected persistent files created with the old Tails version are present in the filesystem 1.199
And all persistent directories from the old Tails version have safe access rights 1.923
After features/support/hooks.rb:331 0.883
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:43.722
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 8.237
And no SquashFS delta is installed 0.275
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.318
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.082
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.348
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.473
When the network is plugged 0.018
And Tor is ready 23.780
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.381
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.739
Given I shutdown Tails and wait for the computer to power off 20.480
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.859
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.262
And the file system changes introduced in version 6.2~testoverlayfs are present 0.271
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.126
# 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.239
When the network is plugged 0.016
And Tor is ready 21.786
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.348
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.279
Given I shutdown Tails and wait for the computer to power off 17.547
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.741
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.387
And only the 6.3~testoverlayfs SquashFS delta is installed 0.108
# 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.138
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.297
When the network is plugged 0.020
And Tor is ready 22.193
Then the Upgrader considers the system as up-to-date 0.094
# 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.219
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.403
After features/support/hooks.rb:331 0.836
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
28.088
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.630
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.601
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the signing key used by the Upgrader is outdated 0.058
But a current signing key is available on our website 0.000
When the network is plugged 0.054
And Tor is ready 19.323
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.379
After features/support/hooks.rb:331 0.704
After features/support/hooks.rb:100 0.000