Project Number Date
test_Tails_ISO_stable 6140 11 Feb 2026, 12:04

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:30.938 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.439
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.074
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.737
When I start Tails from USB drive "old" with network unplugged 48.280
Then the boot device has safe access rights 2.668
And Tails is running from USB drive "old" 0.239
And there is no persistence partition on USB drive "old" 0.049
And process "udev-watchdog" is running 0.046
And udev-watchdog is monitoring the correct device 0.179
And I unplug USB drive "old" 0.134
After features/support/hooks.rb:331 3.678
After features/support/hooks.rb:100 0.033
Tags: @product
1:22.587
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.018
Given a computer 0.079
And I start Tails from USB drive "old" with network unplugged and I login 52.195
Then Tails is running from USB drive "old" 0.277
And I create a persistent partition 24.367
And I take note of which tps features are available 0.682
Then a Tails persistence partition exists on USB drive "old" 0.622
And I shutdown Tails and wait for the computer to power off 4.363
After features/support/hooks.rb:331 0.310
After features/support/hooks.rb:100 0.006
Tags: @product
1:25.888
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:0.266
Then Tails is running from USB drive "old" 0.265
And all tps features are active 1.070
When I write some files expected to persist 1.406
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.157
And all persistence configuration files have safe access rights 0.314
And all persistent directories from the old Tails version have safe access rights 1.959
And I take note of which tps features are available 0.166
And I shutdown Tails and wait for the computer to power off 8.134
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.096
After features/support/hooks.rb:331 0.403
After features/support/hooks.rb:100 0.007
Tags: @product
2:9.966
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.337
And I log in to a new session 10.281
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.744
And I plug USB drive "to_upgrade" 2.284
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.702
Then the running Tails is installed on USB drive "to_upgrade" 15.330
And I unplug USB drive "to_upgrade" 0.133
And I unplug USB drive "__internal" 0.151
After features/support/hooks.rb:331 2.341
After features/support/hooks.rb:100 0.000
Tags: @product
1:8.610
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.051
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.690
Then all tps features from the old Tails version are active 0.924
And Tails is running from USB drive "to_upgrade" 0.235
And the boot device has safe access rights 2.620
And the expected persistent files created with the old Tails version are present in the filesystem 1.208
And all persistent directories from the old Tails version have safe access rights 1.879
After features/support/hooks.rb:331 0.627
After features/support/hooks.rb:100 0.026
Tags: @product @automatic_upgrade
3:57.353
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.034
And no SquashFS delta is installed 0.070
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.043
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.240
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.394
When the network is plugged 0.019
And Tor is ready 13.107
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.054
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.997
Given I shutdown Tails and wait for the computer to power off 9.430
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.879
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.086
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.053
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.119
# 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.216
When the network is plugged 0.016
And Tor is ready 39.054
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.362
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.372
Given I shutdown Tails and wait for the computer to power off 4.310
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.981
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.185
And the file system changes introduced in version 6.3~testoverlayfs are present 0.382
And only the 6.3~testoverlayfs SquashFS delta is installed 0.044
# 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.125
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.197
When the network is plugged 0.017
And Tor is ready 10.845
Then the Upgrader considers the system as up-to-date 10.645
# 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.266
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.353
After features/support/hooks.rb:331 0.657
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
20.091
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 7.558
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.203
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the signing key used by the Upgrader is outdated 0.062
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 9.751
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.451
After features/support/hooks.rb:331 0.682
After features/support/hooks.rb:100 0.000