Project Number Date
test_Tails_ISO_stable 6367 11 May 2026, 12:08

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 12:25.630 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:5.143
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.068
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.038
And I write an old version of the Tails USB image to disk "old" 13.382
When I start Tails from USB drive "old" with network unplugged 47.246
Then the boot device has safe access rights 2.717
And Tails is running from USB drive "old" 0.246
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.060
And udev-watchdog is monitoring the correct device 0.193
And I unplug USB drive "old" 0.136
After features/support/hooks.rb:331 3.451
After features/support/hooks.rb:100 0.034
Tags: @product
1:27.372
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.055
And I start Tails from USB drive "old" with network unplugged and I login 53.139
Then Tails is running from USB drive "old" 0.307
And I create a persistent partition 24.625
And I take note of which tps features are available 0.725
Then a Tails persistence partition exists on USB drive "old" 0.546
And I shutdown Tails and wait for the computer to power off 7.973
After features/support/hooks.rb:331 0.509
After features/support/hooks.rb:100 0.008
Tags: @product
1:28.279
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.068
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.077
Then Tails is running from USB drive "old" 0.244
And all tps features are active 1.213
When I write some files expected to persist 1.440
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.187
And all persistence configuration files have safe access rights 0.487
And all persistent directories from the old Tails version have safe access rights 1.930
And I take note of which tps features are available 0.170
And I shutdown Tails and wait for the computer to power off 7.973
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.484
After features/support/hooks.rb:331 0.555
After features/support/hooks.rb:100 0.007
Tags: @product
2:12.769
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 7.725
And I log in to a new session 12.928
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.731
And I plug USB drive "to_upgrade" 2.225
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.845
Then the running Tails is installed on USB drive "to_upgrade" 17.043
And I unplug USB drive "to_upgrade" 0.138
And I unplug USB drive "__internal" 0.131
After features/support/hooks.rb:331 2.123
After features/support/hooks.rb:100 0.000
Tags: @product
1:11.172
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 "to_upgrade" with network unplugged and I login with persistence enabled 1:4.327
Then all tps features from the old Tails version are active 1.025
And Tails is running from USB drive "to_upgrade" 0.252
And the boot device has safe access rights 2.704
And the expected persistent files created with the old Tails version are present in the filesystem 0.985
And all persistent directories from the old Tails version have safe access rights 1.817
After features/support/hooks.rb:331 0.518
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:36.672
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.296
And no SquashFS delta is installed 0.072
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.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.256
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.383
When the network is plugged 0.033
And Tor is ready 21.307
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.477
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.603
Given I shutdown Tails and wait for the computer to power off 20.268
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.428
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.028
And the file system changes introduced in version 6.2~testoverlayfs are present 0.239
And only the 6.2~testoverlayfs SquashFS delta is installed 0.046
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.140
# 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.213
When the network is plugged 0.028
And Tor is ready 20.355
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.411
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.550
Given I shutdown Tails and wait for the computer to power off 17.229
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.992
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.164
And the file system changes introduced in version 6.3~testoverlayfs are present 0.307
And only the 6.3~testoverlayfs SquashFS delta is installed 0.055
# 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.109
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.200
When the network is plugged 0.022
And Tor is ready 21.240
Then the Upgrader considers the system as up-to-date 0.125
# 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.393
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.408
After features/support/hooks.rb:331 0.809
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
24.220
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 7.514
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.044
And the signing key used by the Upgrader is outdated 0.049
But a current signing key is available on our website 0.000
When the network is plugged 0.019
And Tor is ready 16.005
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.359
After features/support/hooks.rb:331 1.006
After features/support/hooks.rb:100 0.000