Project Number Date
test_Tails_ISO_stable 6056 13 Jan 2026, 13:17

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:27.099 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:7.276
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.050
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.398
When I start Tails from USB drive "old" with network unplugged 49.315
Then the boot device has safe access rights 2.722
And Tails is running from USB drive "old" 0.240
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.051
And udev-watchdog is monitoring the correct device 0.245
And I unplug USB drive "old" 0.163
After features/support/hooks.rb:331 4.029
After features/support/hooks.rb:100 0.006
Tags: @product
1:26.183
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.084
And I start Tails from USB drive "old" with network unplugged and I login 52.186
Then Tails is running from USB drive "old" 0.233
And I create a persistent partition 24.200
And I take note of which tps features are available 0.833
Then a Tails persistence partition exists on USB drive "old" 0.617
And I shutdown Tails and wait for the computer to power off 8.027
After features/support/hooks.rb:331 0.258
After features/support/hooks.rb:100 0.006
Tags: @product
1:19.801
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.061
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.089
Then Tails is running from USB drive "old" 0.303
And all tps features are active 1.042
When I write some files expected to persist 1.109
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.143
And all persistence configuration files have safe access rights 0.287
And all persistent directories from the old Tails version have safe access rights 1.762
And I take note of which tps features are available 0.143
And I shutdown Tails and wait for the computer to power off 3.937
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.921
After features/support/hooks.rb:331 0.563
After features/support/hooks.rb:100 0.007
Tags: @product
2:10.821
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 without a persistent partition and stopped at Tails Greeter's login screen 8.435
And I log in to a new session 10.785
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.763
And I plug USB drive "to_upgrade" 2.229
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.685
Then the running Tails is installed on USB drive "to_upgrade" 15.648
And I unplug USB drive "to_upgrade" 0.128
And I unplug USB drive "__internal" 0.144
After features/support/hooks.rb:331 3.801
After features/support/hooks.rb:100 0.000
Tags: @product
1:8.955
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.063
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.966
Then all tps features from the old Tails version are active 1.060
And Tails is running from USB drive "to_upgrade" 0.224
And the boot device has safe access rights 2.594
And the expected persistent files created with the old Tails version are present in the filesystem 1.168
And all persistent directories from the old Tails version have safe access rights 1.877
After features/support/hooks.rb:331 0.751
After features/support/hooks.rb:100 0.029
Tags: @product @automatic_upgrade
3:53.726
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.226
And no SquashFS delta is installed 0.068
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.258
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.249
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.344
When the network is plugged 0.017
And Tor is ready 42.489
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.403
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.886
Given I shutdown Tails and wait for the computer to power off 9.448
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.992
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.158
And the file system changes introduced in version 6.2~testoverlayfs are present 0.194
And only the 6.2~testoverlayfs SquashFS delta is installed 0.048
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.146
# 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.207
When the network is plugged 0.015
And Tor is ready 11.159
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.371
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.287
Given I shutdown Tails and wait for the computer to power off 7.916
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.277
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.104
And the file system changes introduced in version 6.3~testoverlayfs are present 0.353
And only the 6.3~testoverlayfs SquashFS delta is installed 0.041
# 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.119
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.185
When the network is plugged 0.016
And Tor is ready 11.199
Then the Upgrader considers the system as up-to-date 0.105
# 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 3.984
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.386
After features/support/hooks.rb:331 0.776
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
20.335
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 7.316
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.252
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the signing key used by the Upgrader is outdated 0.050
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 9.496
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.160
After features/support/hooks.rb:331 0.837
After features/support/hooks.rb:100 0.000