Project Number Date
test_Tails_ISO_stable 6092 26 Jan 2026, 11:46

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:34.498 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:17.056
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.055
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.988
When I start Tails from USB drive "old" with network unplugged 58.260
Then the boot device has safe access rights 2.965
And Tails is running from USB drive "old" 0.256
And there is no persistence partition on USB drive "old" 0.045
And process "udev-watchdog" is running 0.086
And udev-watchdog is monitoring the correct device 0.232
And I unplug USB drive "old" 0.141
After features/support/hooks.rb:331 3.808
After features/support/hooks.rb:100 0.006
Tags: @product
1:28.049
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.083
And I start Tails from USB drive "old" with network unplugged and I login 53.501
Then Tails is running from USB drive "old" 0.264
And I create a persistent partition 24.845
And I take note of which tps features are available 0.709
Then a Tails persistence partition exists on USB drive "old" 0.559
And I shutdown Tails and wait for the computer to power off 8.085
After features/support/hooks.rb:331 0.275
After features/support/hooks.rb:100 0.006
Tags: @product
1:21.653
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.087
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.101
Then Tails is running from USB drive "old" 0.355
And all tps features are active 1.193
When I write some files expected to persist 1.345
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.206
And all persistence configuration files have safe access rights 0.288
And all persistent directories from the old Tails version have safe access rights 1.985
And I take note of which tps features are available 0.184
And I shutdown Tails and wait for the computer to power off 2.694
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.210
After features/support/hooks.rb:331 0.193
After features/support/hooks.rb:100 0.007
Tags: @product
2:11.603
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.683
And I log in to a new session 11.373
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.768
And I plug USB drive "to_upgrade" 2.254
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.086
Then the running Tails is installed on USB drive "to_upgrade" 15.169
And I unplug USB drive "to_upgrade" 0.130
And I unplug USB drive "__internal" 0.137
After features/support/hooks.rb:331 2.187
After features/support/hooks.rb:100 0.000
Tags: @product
1:9.972
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.052
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.451
Then all tps features from the old Tails version are active 1.306
And Tails is running from USB drive "to_upgrade" 0.314
And the boot device has safe access rights 2.744
And the expected persistent files created with the old Tails version are present in the filesystem 1.130
And all persistent directories from the old Tails version have safe access rights 1.972
After features/support/hooks.rb:331 0.809
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
3:44.798
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 8.234
And no SquashFS delta is installed 0.180
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.192
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.255
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.365
When the network is plugged 0.019
And Tor is ready 13.799
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.354
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.895
Given I shutdown Tails and wait for the computer to power off 11.152
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.857
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.137
And the file system changes introduced in version 6.2~testoverlayfs are present 0.213
And only the 6.2~testoverlayfs SquashFS delta is installed 0.050
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.125
# 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.015
And Tor is ready 11.446
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.722
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.148
Given I shutdown Tails and wait for the computer to power off 8.130
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.789
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.292
And the file system changes introduced in version 6.3~testoverlayfs are present 0.423
And only the 6.3~testoverlayfs SquashFS delta is installed 0.056
# 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.230
When the network is plugged 0.018
And Tor is ready 11.066
Then the Upgrader considers the system as up-to-date 10.584
# 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.251
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.355
After features/support/hooks.rb:331 0.684
After features/support/hooks.rb:100 0.069
Tags: @product @automatic_upgrade
21.364
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.903
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.315
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
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.014
And Tor is ready 9.972
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.042
After features/support/hooks.rb:331 0.902
After features/support/hooks.rb:100 0.000