Project Number Date
test_Tails_ISO_stable 6253 01 Apr 2026, 11:13

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:33.123 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:20.595
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given a computer 0.084
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 15.420
When I start Tails from USB drive "old" with network unplugged 59.845
Then the boot device has safe access rights 3.408
And Tails is running from USB drive "old" 0.243
And there is no persistence partition on USB drive "old" 0.090
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.235
And I unplug USB drive "old" 0.145
After features/support/hooks.rb:331 1.749
After features/support/hooks.rb:100 0.008
Tags: @product
1:37.958
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.088
And I start Tails from USB drive "old" with network unplugged and I login 1:0.546
Then Tails is running from USB drive "old" 0.315
And I create a persistent partition 27.815
And I take note of which tps features are available 0.831
Then a Tails persistence partition exists on USB drive "old" 0.860
And I shutdown Tails and wait for the computer to power off 7.501
After features/support/hooks.rb:331 0.430
After features/support/hooks.rb:100 0.007
Tags: @product
1:34.607
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.102
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:9.496
Then Tails is running from USB drive "old" 0.274
And all tps features are active 1.323
When I write some files expected to persist 1.549
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.178
And all persistence configuration files have safe access rights 0.957
And all persistent directories from the old Tails version have safe access rights 2.748
And I take note of which tps features are available 0.220
And I shutdown Tails and wait for the computer to power off 4.291
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.465
After features/support/hooks.rb:331 0.322
After features/support/hooks.rb:100 0.023
Tags: @product
2:18.521
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.823
And I log in to a new session 14.086
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.960
And I plug USB drive "to_upgrade" 2.282
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.010
Then the running Tails is installed on USB drive "to_upgrade" 17.915
And I unplug USB drive "to_upgrade" 0.219
And I unplug USB drive "__internal" 0.222
After features/support/hooks.rb:331 2.953
After features/support/hooks.rb:100 0.000
Tags: @product
1:17.391
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.093
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:9.569
Then all tps features from the old Tails version are active 0.924
And Tails is running from USB drive "to_upgrade" 0.247
And the boot device has safe access rights 2.875
And the expected persistent files created with the old Tails version are present in the filesystem 1.400
And all persistent directories from the old Tails version have safe access rights 2.279
After features/support/hooks.rb:331 0.984
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
4:55.073
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 with a persistent partition enabled and logged in 8.993
And no SquashFS delta is installed 0.066
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.230
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.245
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.393
When the network is plugged 0.014
And Tor is ready 22.168
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.385
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.083
Given I shutdown Tails and wait for the computer to power off 15.621
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:23.388
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.600
And the file system changes introduced in version 6.2~testoverlayfs are present 0.238
And only the 6.2~testoverlayfs SquashFS delta is installed 0.064
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.207
# 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.280
When the network is plugged 0.015
And Tor is ready 22.411
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.455
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.081
Given I shutdown Tails and wait for the computer to power off 17.907
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:20.057
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.184
And the file system changes introduced in version 6.3~testoverlayfs are present 0.331
And only the 6.3~testoverlayfs SquashFS delta is installed 0.059
# 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.177
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.272
When the network is plugged 0.017
And Tor is ready 22.199
Then the Upgrader considers the system as up-to-date 0.110
# 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.361
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.373
After features/support/hooks.rb:331 1.124
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
28.975
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 with a persistent partition enabled and logged in 8.759
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.275
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.113
And the signing key used by the Upgrader is outdated 0.123
But a current signing key is available on our website 0.000
When the network is plugged 0.038
And Tor is ready 19.216
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.448
After features/support/hooks.rb:331 0.811
After features/support/hooks.rb:100 0.000