Project Number Date
test_Tails_ISO_stable 6074 17 Jan 2026, 08:00

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:20.537 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:15.378
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.054
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 13.628
When I start Tails from USB drive "old" with network unplugged 57.162
Then the boot device has safe access rights 2.757
And Tails is running from USB drive "old" 0.282
And there is no persistence partition on USB drive "old" 0.038
And process "udev-watchdog" is running 0.067
And udev-watchdog is monitoring the correct device 0.211
And I unplug USB drive "old" 0.151
After features/support/hooks.rb:331 3.771
After features/support/hooks.rb:100 0.007
Tags: @product
1:27.807
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.046
And I start Tails from USB drive "old" with network unplugged and I login 53.950
Then Tails is running from USB drive "old" 0.254
And I create a persistent partition 24.066
And I take note of which tps features are available 0.723
Then a Tails persistence partition exists on USB drive "old" 0.694
And I shutdown Tails and wait for the computer to power off 8.070
After features/support/hooks.rb:331 0.579
After features/support/hooks.rb:100 0.007
Tags: @product
1:24.379
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.049
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.183
Then Tails is running from USB drive "old" 0.280
And all tps features are active 1.242
When I write some files expected to persist 1.417
# 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.319
And all persistent directories from the old Tails version have safe access rights 2.186
And I take note of which tps features are available 0.184
And I shutdown Tails and wait for the computer to power off 4.084
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.245
After features/support/hooks.rb:331 0.448
After features/support/hooks.rb:100 0.007
Tags: @product
2:12.837
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.926
And I log in to a new session 11.513
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.037
And I plug USB drive "to_upgrade" 2.227
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.335
Then the running Tails is installed on USB drive "to_upgrade" 15.508
And I unplug USB drive "to_upgrade" 0.157
And I unplug USB drive "__internal" 0.130
After features/support/hooks.rb:331 4.015
After features/support/hooks.rb:100 0.000
Tags: @product
1:9.754
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.054
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.560
Then all tps features from the old Tails version are active 0.936
And Tails is running from USB drive "to_upgrade" 0.291
And the boot device has safe access rights 2.694
And the expected persistent files created with the old Tails version are present in the filesystem 1.194
And all persistent directories from the old Tails version have safe access rights 2.023
After features/support/hooks.rb:331 0.956
After features/support/hooks.rb:100 0.049
Tags: @product @automatic_upgrade
3:30.736
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.081
And no SquashFS delta is installed 0.058
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.197
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.382
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.589
When the network is plugged 0.016
And Tor is ready 12.391
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.774
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.811
Given I shutdown Tails and wait for the computer to power off 9.912
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.084
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.010
And the file system changes introduced in version 6.2~testoverlayfs are present 0.238
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.129
# 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.194
When the network is plugged 0.013
And Tor is ready 11.944
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.160
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.173
Given I shutdown Tails and wait for the computer to power off 7.936
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.769
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.254
And the file system changes introduced in version 6.3~testoverlayfs are present 0.436
And only the 6.3~testoverlayfs SquashFS delta is installed 0.066
# 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.139
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.265
When the network is plugged 0.015
And Tor is ready 11.666
Then the Upgrader considers the system as up-to-date 0.096
# 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.427
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.391
After features/support/hooks.rb:331 0.680
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
19.643
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.914
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.230
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the signing key used by the Upgrader is outdated 0.051
But a current signing key is available on our website 0.000
When the network is plugged 0.019
And Tor is ready 10.196
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.188
After features/support/hooks.rb:331 0.623
After features/support/hooks.rb:100 0.000