Project Number Date
test_Tails_ISO_stable 6361 08 May 2026, 18:12

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:50.666 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
57.534
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.045
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.186
When I start Tails from USB drive "old" with network unplugged 40.089
Then the boot device has safe access rights 2.541
And Tails is running from USB drive "old" 0.228
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.040
And udev-watchdog is monitoring the correct device 0.194
And I unplug USB drive "old" 0.138
After features/support/hooks.rb:331 3.502
After features/support/hooks.rb:100 0.008
Tags: @product
1:18.759
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.069
And I start Tails from USB drive "old" with network unplugged and I login 51.132
Then Tails is running from USB drive "old" 0.215
And I create a persistent partition 23.585
And I take note of which tps features are available 0.623
Then a Tails persistence partition exists on USB drive "old" 0.498
And I shutdown Tails and wait for the computer to power off 2.632
After features/support/hooks.rb:331 0.558
After features/support/hooks.rb:100 0.006
Tags: @product
1:21.046
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.049
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.706
Then Tails is running from USB drive "old" 0.226
And all tps features are active 1.109
When I write some files expected to persist 1.289
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.154
And all persistence configuration files have safe access rights 0.563
And all persistent directories from the old Tails version have safe access rights 2.023
And I take note of which tps features are available 0.142
And I shutdown Tails and wait for the computer to power off 4.214
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.567
After features/support/hooks.rb:331 0.305
After features/support/hooks.rb:100 0.007
Tags: @product
2:9.067
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 7.626
And I log in to a new session 12.215
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.763
And I plug USB drive "to_upgrade" 2.273
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.849
Then the running Tails is installed on USB drive "to_upgrade" 15.062
And I unplug USB drive "to_upgrade" 0.132
And I unplug USB drive "__internal" 0.143
After features/support/hooks.rb:331 1.950
After features/support/hooks.rb:100 0.000
Tags: @product
1:8.089
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.051
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.552
Then all tps features from the old Tails version are active 0.941
And Tails is running from USB drive "to_upgrade" 0.210
And the boot device has safe access rights 2.413
And the expected persistent files created with the old Tails version are present in the filesystem 1.060
And all persistent directories from the old Tails version have safe access rights 1.859
After features/support/hooks.rb:331 0.617
After features/support/hooks.rb:100 0.026
4:29.510
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.321
And no SquashFS delta is installed 0.061
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.226
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.219
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.370
When the network is plugged 0.028
And Tor is ready 20.673
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.377
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.378
Given I shutdown Tails and wait for the computer to power off 19.736
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.734
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.117
And the file system changes introduced in version 6.2~testoverlayfs are present 0.240
And only the 6.2~testoverlayfs SquashFS delta is installed 0.050
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.131
# 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.016
And Tor is ready 20.273
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.346
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.708
Given I shutdown Tails and wait for the computer to power off 18.622
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.288
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.062
And the file system changes introduced in version 6.3~testoverlayfs are present 0.391
And only the 6.3~testoverlayfs SquashFS delta is installed 0.044
# 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.128
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.208
When the network is plugged 0.016
And Tor is ready 20.639
Then the Upgrader considers the system as up-to-date 0.126
# 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.291
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.365
After features/support/hooks.rb:331 0.904
After features/support/hooks.rb:100 0.011
26.658
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.201
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.221
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.064
But a current signing key is available on our website 0.000
When the network is plugged 0.027
And Tor is ready 18.723
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.368
After features/support/hooks.rb:331 0.517
After features/support/hooks.rb:100 0.000