Project Number Date
test_Tails_ISO_stable 6323 22 Apr 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 13:27.539 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.434
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.063
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 14.965
When I start Tails from USB drive "old" with network unplugged 43.743
Then the boot device has safe access rights 2.913
And Tails is running from USB drive "old" 0.242
And there is no persistence partition on USB drive "old" 0.080
And process "udev-watchdog" is running 0.053
And udev-watchdog is monitoring the correct device 0.210
And I unplug USB drive "old" 0.135
After features/support/hooks.rb:331 3.704
After features/support/hooks.rb:100 0.006
Tags: @product
1:30.955
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.171
And I start Tails from USB drive "old" with network unplugged and I login 58.162
Then Tails is running from USB drive "old" 0.299
And I create a persistent partition 26.795
And I take note of which tps features are available 0.771
Then a Tails persistence partition exists on USB drive "old" 0.626
And I shutdown Tails and wait for the computer to power off 4.129
After features/support/hooks.rb:331 0.509
After features/support/hooks.rb:100 0.007
Tags: @product
1:31.030
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.061
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.964
Then Tails is running from USB drive "old" 0.698
And all tps features are active 1.488
When I write some files expected to persist 1.666
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.214
And all persistence configuration files have safe access rights 0.567
And all persistent directories from the old Tails version have safe access rights 2.387
And I take note of which tps features are available 0.200
And I shutdown Tails and wait for the computer to power off 4.157
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.623
After features/support/hooks.rb:331 0.392
After features/support/hooks.rb:100 0.010
Tags: @product
2:22.120
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.414
And I log in to a new session 19.476
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.775
And I plug USB drive "to_upgrade" 2.217
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.872
Then the running Tails is installed on USB drive "to_upgrade" 16.963
And I unplug USB drive "to_upgrade" 0.187
And I unplug USB drive "__internal" 0.212
After features/support/hooks.rb:331 3.845
After features/support/hooks.rb:100 0.000
Tags: @product
1:17.190
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.090
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.576
Then all tps features from the old Tails version are active 1.114
And Tails is running from USB drive "to_upgrade" 0.322
And the boot device has safe access rights 3.458
And the expected persistent files created with the old Tails version are present in the filesystem 1.367
And all persistent directories from the old Tails version have safe access rights 2.259
After features/support/hooks.rb:331 0.549
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
5:12.920
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.919
And no SquashFS delta is installed 0.115
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.308
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.232
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.443
When the network is plugged 0.019
And Tor is ready 44.781
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.417
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.049
Given I shutdown Tails and wait for the computer to power off 16.905
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.924
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 1.329
And the file system changes introduced in version 6.2~testoverlayfs are present 0.215
And only the 6.2~testoverlayfs SquashFS delta is installed 0.040
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.141
# 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.240
When the network is plugged 0.033
And Tor is ready 21.559
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.440
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.992
Given I shutdown Tails and wait for the computer to power off 17.746
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.997
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 1.141
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.054
# 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.156
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.236
When the network is plugged 0.016
And Tor is ready 22.881
Then the Upgrader considers the system as up-to-date 0.144
# 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.389
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.585
After features/support/hooks.rb:331 0.785
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
29.888
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.531
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.415
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 0.048
But a current signing key is available on our website 0.000
When the network is plugged 0.021
And Tor is ready 20.417
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.393
After features/support/hooks.rb:331 0.846
After features/support/hooks.rb:100 0.000