Project Number Date
test_Tails_ISO_stable 6408 27 May 2026, 19: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 11:7.010 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:10.126
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.048
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.180
When I start Tails from USB drive "old" with network unplugged 52.552
Then the boot device has safe access rights 2.643
And Tails is running from USB drive "old" 0.222
And there is no persistence partition on USB drive "old" 0.048
And process "udev-watchdog" is running 0.054
And udev-watchdog is monitoring the correct device 0.210
And I unplug USB drive "old" 0.137
After features/support/hooks.rb:335 3.473
After features/support/hooks.rb:104 0.008
Tags: @product
1:24.440
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.057
And I start Tails from USB drive "old" with network unplugged and I login 52.104
Then Tails is running from USB drive "old" 0.254
And I create a persistent partition 24.497
And I take note of which tps features are available 0.304
Then a Tails persistence partition exists on USB drive "old" 0.512
And I shutdown Tails and wait for the computer to power off 6.710
After features/support/hooks.rb:335 0.423
After features/support/hooks.rb:104 0.006
Tags: @product
1:21.529
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.053
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.217
Then Tails is running from USB drive "old" 0.234
And all tps features are active 1.107
When I write some files expected to persist 1.219
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.171
And all persistence configuration files have safe access rights 0.290
And all persistent directories from the old Tails version have safe access rights 1.927
And I take note of which tps features are available 0.147
And I shutdown Tails and wait for the computer to power off 5.499
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 11.661
After features/support/hooks.rb:335 0.302
After features/support/hooks.rb:104 0.006
Tags: @product
2:7.740
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 7.763
And I log in to a new session 11.887
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.683
And I plug USB drive "to_upgrade" 2.270
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.862
Then the running Tails is installed on USB drive "to_upgrade" 14.011
And I unplug USB drive "to_upgrade" 0.134
And I unplug USB drive "__internal" 0.127
After features/support/hooks.rb:335 2.064
After features/support/hooks.rb:104 0.000
Tags: @product
1:8.141
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.060
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.930
Then all tps features from the old Tails version are active 1.025
And Tails is running from USB drive "to_upgrade" 0.237
And the boot device has safe access rights 2.712
And the expected persistent files created with the old Tails version are present in the filesystem 1.209
And all persistent directories from the old Tails version have safe access rights 1.966
After features/support/hooks.rb:335 0.532
After features/support/hooks.rb:104 0.006
Tags: @product @automatic_upgrade
3:34.180
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.089
And no SquashFS delta is installed 0.072
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.205
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.217
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.329
When the network is plugged 0.015
And Tor is ready 12.453
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.116
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.322
Given I shutdown Tails and wait for the computer to power off 10.983
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.537
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.096
And the file system changes introduced in version 6.2~testoverlayfs are present 0.263
And only the 6.2~testoverlayfs SquashFS delta is installed 0.063
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.196
# 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.204
When the network is plugged 0.020
And Tor is ready 10.651
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.816
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.010
Given I shutdown Tails and wait for the computer to power off 5.427
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.391
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.068
And the file system changes introduced in version 6.3~testoverlayfs are present 0.364
And only the 6.3~testoverlayfs SquashFS delta is installed 0.050
# 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.126
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.184
When the network is plugged 0.013
And Tor is ready 10.895
Then the Upgrader considers the system as up-to-date 10.475
# 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.110
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.338
After features/support/hooks.rb:335 0.920
After features/support/hooks.rb:104 0.012
Tags: @product @automatic_upgrade
20.851
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.432
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.257
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
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.019
And Tor is ready 9.779
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.266
After features/support/hooks.rb:335 0.886
After features/support/hooks.rb:104 0.000