Project Number Date
test_Tails_ISO_stable 6357 07 May 2026, 11:30

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 12:14.015 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
57.842
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.056
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 13.316
When I start Tails from USB drive "old" with network unplugged 40.150
Then the boot device has safe access rights 2.625
And Tails is running from USB drive "old" 0.247
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.065
And udev-watchdog is monitoring the correct device 0.185
And I unplug USB drive "old" 0.127
After features/support/hooks.rb:331 1.236
After features/support/hooks.rb:100 0.006
Tags: @product
1:25.200
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login 52.206
Then Tails is running from USB drive "old" 0.241
And I create a persistent partition 24.599
And I take note of which tps features are available 0.726
Then a Tails persistence partition exists on USB drive "old" 0.547
And I shutdown Tails and wait for the computer to power off 6.827
After features/support/hooks.rb:331 0.195
After features/support/hooks.rb:100 0.006
Tags: @product
1:28.256
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.053
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.717
Then Tails is running from USB drive "old" 0.229
And all tps features are active 1.162
When I write some files expected to persist 1.372
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.174
And all persistence configuration files have safe access rights 0.505
And all persistent directories from the old Tails version have safe access rights 1.981
And I take note of which tps features are available 0.164
And I shutdown Tails and wait for the computer to power off 8.346
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.549
After features/support/hooks.rb:331 0.580
After features/support/hooks.rb:100 0.007
Tags: @product
2:11.586
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.115
And I log in to a new session 12.200
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.713
And I plug USB drive "to_upgrade" 2.253
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.670
Then the running Tails is installed on USB drive "to_upgrade" 16.368
And I unplug USB drive "to_upgrade" 0.129
And I unplug USB drive "__internal" 0.135
After features/support/hooks.rb:331 2.159
After features/support/hooks.rb:100 0.000
Tags: @product
1:8.639
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.064
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.807
Then all tps features from the old Tails version are active 1.026
And Tails is running from USB drive "to_upgrade" 0.264
And the boot device has safe access rights 2.469
And the expected persistent files created with the old Tails version are present in the filesystem 1.079
And all persistent directories from the old Tails version have safe access rights 1.928
After features/support/hooks.rb:331 0.612
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
4:34.955
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.317
And no SquashFS delta is installed 0.070
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.220
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.253
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.330
When the network is plugged 0.019
And Tor is ready 20.191
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.443
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.938
Given I shutdown Tails and wait for the computer to power off 20.085
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.003
Then Tails is running version 6.2~testoverlayfs 0.009
And all tps features are active 1.258
And the file system changes introduced in version 6.2~testoverlayfs are present 0.247
And only the 6.2~testoverlayfs SquashFS delta is installed 0.063
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.155
# 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.223
When the network is plugged 0.021
And Tor is ready 20.965
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.426
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.529
Given I shutdown Tails and wait for the computer to power off 12.186
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.128
Then Tails is running version 6.3~testoverlayfs 0.009
And all tps features are active 1.343
And the file system changes introduced in version 6.3~testoverlayfs are present 0.411
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.229
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.248
When the network is plugged 0.016
And Tor is ready 21.563
Then the Upgrader considers the system as up-to-date 0.145
# 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.384
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.397
After features/support/hooks.rb:331 1.052
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
27.533
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 7.867
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.256
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the signing key used by the Upgrader is outdated 0.065
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 18.862
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.400
After features/support/hooks.rb:331 0.805
After features/support/hooks.rb:100 0.000