Project Number Date
test_Tails_ISO_stable 6353 05 May 2026, 13:25

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:10.290 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:11.226
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.090
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 14.880
When I start Tails from USB drive "old" with network unplugged 50.739
Then the boot device has safe access rights 3.749
And Tails is running from USB drive "old" 0.255
And there is no persistence partition on USB drive "old" 0.049
And process "udev-watchdog" is running 0.069
And udev-watchdog is monitoring the correct device 0.220
And I unplug USB drive "old" 0.140
After features/support/hooks.rb:331 1.469
After features/support/hooks.rb:100 0.011
Tags: @product
1:34.528
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.088
And I start Tails from USB drive "old" with network unplugged and I login 59.215
Then Tails is running from USB drive "old" 0.271
And I create a persistent partition 25.272
And I take note of which tps features are available 0.742
Then a Tails persistence partition exists on USB drive "old" 0.604
And I shutdown Tails and wait for the computer to power off 8.333
After features/support/hooks.rb:331 0.411
After features/support/hooks.rb:100 0.008
Tags: @product
1:34.281
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.131
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:8.065
Then Tails is running from USB drive "old" 0.335
And all tps features are active 1.210
When I write some files expected to persist 1.248
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.189
And all persistence configuration files have safe access rights 0.446
And all persistent directories from the old Tails version have safe access rights 2.400
And I take note of which tps features are available 0.204
And I shutdown Tails and wait for the computer to power off 7.286
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.763
After features/support/hooks.rb:331 0.571
After features/support/hooks.rb:100 0.008
Tags: @product
2:14.843
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 without a persistent partition and stopped at Tails Greeter's login screen 8.609
And I log in to a new session 12.803
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.007
And I plug USB drive "to_upgrade" 2.350
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.492
Then the running Tails is installed on USB drive "to_upgrade" 17.306
And I unplug USB drive "to_upgrade" 0.142
And I unplug USB drive "__internal" 0.131
After features/support/hooks.rb:331 2.096
After features/support/hooks.rb:100 0.000
Tags: @product
1:18.428
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.054
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:10.198
Then all tps features from the old Tails version are active 1.379
And Tails is running from USB drive "to_upgrade" 0.290
And the boot device has safe access rights 3.143
And the expected persistent files created with the old Tails version are present in the filesystem 1.306
And all persistent directories from the old Tails version have safe access rights 2.055
After features/support/hooks.rb:331 0.819
After features/support/hooks.rb:100 0.032
Tags: @product @automatic_upgrade
4:49.673
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.844
And no SquashFS delta is installed 0.068
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.213
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.081
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.343
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.515
When the network is plugged 0.026
And Tor is ready 21.824
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.471
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.815
Given I shutdown Tails and wait for the computer to power off 15.099
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:21.213
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.424
And the file system changes introduced in version 6.2~testoverlayfs are present 0.367
And only the 6.2~testoverlayfs SquashFS delta is installed 0.056
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.189
# 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.218
When the network is plugged 0.018
And Tor is ready 21.871
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.415
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.492
Given I shutdown Tails and wait for the computer to power off 18.654
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.436
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.325
And the file system changes introduced in version 6.3~testoverlayfs are present 0.457
And only the 6.3~testoverlayfs SquashFS delta is installed 0.052
# 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.151
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.276
When the network is plugged 0.021
And Tor is ready 21.128
Then the Upgrader considers the system as up-to-date 0.123
# 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.042
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.416
After features/support/hooks.rb:331 0.899
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
27.307
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.014
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.228
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.053
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 18.536
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.410
After features/support/hooks.rb:331 0.922
After features/support/hooks.rb:100 0.000