Project Number Date
test_Tails_ISO_stable 6266 06 Apr 2026, 11:26

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:57.487 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:55.032
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.159
And I create a 7200 MiB disk named "old" 0.014
And I plug USB drive "old" 1.037
And I write an old version of the Tails USB image to disk "old" 14.653
When I start Tails from USB drive "old" with network unplugged 1:35.533
Then the boot device has safe access rights 2.926
And Tails is running from USB drive "old" 0.244
And there is no persistence partition on USB drive "old" 0.049
And process "udev-watchdog" is running 0.065
And udev-watchdog is monitoring the correct device 0.205
And I unplug USB drive "old" 0.143
After features/support/hooks.rb:331 1.453
After features/support/hooks.rb:100 0.007
Tags: @product
1:34.785
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.059
And I start Tails from USB drive "old" with network unplugged and I login 59.451
Then Tails is running from USB drive "old" 0.262
And I create a persistent partition 25.282
And I take note of which tps features are available 0.770
Then a Tails persistence partition exists on USB drive "old" 0.625
And I shutdown Tails and wait for the computer to power off 8.332
After features/support/hooks.rb:331 0.150
After features/support/hooks.rb:100 0.006
Tags: @product
1:28.675
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.075
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.173
Then Tails is running from USB drive "old" 0.272
And all tps features are active 1.183
When I write some files expected to persist 1.316
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.250
And all persistence configuration files have safe access rights 0.462
And all persistent directories from the old Tails version have safe access rights 2.062
And I take note of which tps features are available 0.158
And I shutdown Tails and wait for the computer to power off 8.264
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.454
After features/support/hooks.rb:331 0.159
After features/support/hooks.rb:100 0.009
Tags: @product
2:30.856
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 without a persistent partition and stopped at Tails Greeter's login screen 8.956
And I log in to a new session 25.303
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.797
And I plug USB drive "to_upgrade" 2.262
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.279
Then the running Tails is installed on USB drive "to_upgrade" 15.929
And I unplug USB drive "to_upgrade" 0.154
And I unplug USB drive "__internal" 0.174
After features/support/hooks.rb:331 3.909
After features/support/hooks.rb:100 0.000
Tags: @product
1:14.228
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.055
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.520
Then all tps features from the old Tails version are active 1.220
And Tails is running from USB drive "to_upgrade" 0.215
And the boot device has safe access rights 2.852
And the expected persistent files created with the old Tails version are present in the filesystem 1.387
And all persistent directories from the old Tails version have safe access rights 1.976
After features/support/hooks.rb:331 0.579
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:43.829
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 8.359
And no SquashFS delta is installed 0.102
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.235
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
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.389
When the network is plugged 0.026
And Tor is ready 23.494
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.416
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.001
Given I shutdown Tails and wait for the computer to power off 20.685
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.786
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.329
And the file system changes introduced in version 6.2~testoverlayfs are present 0.247
And only the 6.2~testoverlayfs SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.170
# 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.260
When the network is plugged 0.020
And Tor is ready 20.724
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.380
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.302
Given I shutdown Tails and wait for the computer to power off 17.291
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.482
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.378
And the file system changes introduced in version 6.3~testoverlayfs are present 0.433
And only the 6.3~testoverlayfs SquashFS delta is installed 0.061
# 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.147
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.232
When the network is plugged 0.015
And Tor is ready 22.221
Then the Upgrader considers the system as up-to-date 0.130
# 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.732
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.407
After features/support/hooks.rb:331 0.876
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
30.080
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.828
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.401
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.056
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 21.302
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.420
After features/support/hooks.rb:331 0.811
After features/support/hooks.rb:100 0.000