Project Number Date
test_Tails_ISO_stable 6294 14 Apr 2026, 12:40

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:28.124 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:6.726
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.099
And I create a 7200 MiB disk named "old" 0.012
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 14.664
When I start Tails from USB drive "old" with network unplugged 46.869
Then the boot device has safe access rights 3.245
And Tails is running from USB drive "old" 0.302
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.060
And udev-watchdog is monitoring the correct device 0.220
And I unplug USB drive "old" 0.162
After features/support/hooks.rb:331 3.427
After features/support/hooks.rb:100 0.008
Tags: @product
1:32.077
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.083
And I start Tails from USB drive "old" with network unplugged and I login 57.672
Then Tails is running from USB drive "old" 0.330
And I create a persistent partition 23.856
And I take note of which tps features are available 0.839
Then a Tails persistence partition exists on USB drive "old" 0.640
And I shutdown Tails and wait for the computer to power off 8.654
After features/support/hooks.rb:331 0.351
After features/support/hooks.rb:100 0.010
Tags: @product
1:31.679
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.134
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.360
Then Tails is running from USB drive "old" 0.301
And all tps features are active 1.212
When I write some files expected to persist 1.298
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.198
And all persistence configuration files have safe access rights 0.427
And all persistent directories from the old Tails version have safe access rights 1.976
And I take note of which tps features are available 0.239
And I shutdown Tails and wait for the computer to power off 8.197
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.334
After features/support/hooks.rb:331 0.171
After features/support/hooks.rb:100 0.011
Tags: @product
2:21.295
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.784
And I log in to a new session 17.352
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.002
And I plug USB drive "to_upgrade" 2.277
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.864
Then the running Tails is installed on USB drive "to_upgrade" 18.701
And I unplug USB drive "to_upgrade" 0.155
And I unplug USB drive "__internal" 0.157
After features/support/hooks.rb:331 2.640
After features/support/hooks.rb:100 0.000
Tags: @product
1:20.249
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Given a computer 0.092
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:12.598
Then all tps features from the old Tails version are active 1.077
And Tails is running from USB drive "to_upgrade" 0.277
And the boot device has safe access rights 2.672
And the expected persistent files created with the old Tails version are present in the filesystem 1.240
And all persistent directories from the old Tails version have safe access rights 2.290
After features/support/hooks.rb:331 0.639
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
5:4.982
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 9.508
And no SquashFS delta is installed 0.068
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.285
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.241
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.380
When the network is plugged 0.024
And Tor is ready 27.676
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.425
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.623
Given I shutdown Tails and wait for the computer to power off 20.415
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:22.292
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 1.189
And the file system changes introduced in version 6.2~testoverlayfs are present 0.279
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.149
# 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.239
When the network is plugged 0.022
And Tor is ready 22.267
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.417
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.004
Given I shutdown Tails and wait for the computer to power off 18.012
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.671
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.203
And the file system changes introduced in version 6.3~testoverlayfs are present 0.424
And only the 6.3~testoverlayfs SquashFS delta is installed 0.046
# 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.155
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.213
When the network is plugged 0.017
And Tor is ready 23.283
Then the Upgrader considers the system as up-to-date 0.170
# 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 5.691
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.453
After features/support/hooks.rb:331 1.101
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
31.112
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 with a persistent partition enabled and logged in 8.379
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.375
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the signing key used by the Upgrader is outdated 0.059
But a current signing key is available on our website 0.000
When the network is plugged 0.034
And Tor is ready 21.759
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.455
After features/support/hooks.rb:331 0.938
After features/support/hooks.rb:100 0.000