Project Number Date
test_Tails_ISO_devel 4385 08 May 2026, 20:09

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:57.575 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:3.142
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.057
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 12.877
When I start Tails from USB drive "old" with network unplugged 46.063
Then the boot device has safe access rights 2.503
And Tails is running from USB drive "old" 0.228
And there is no persistence partition on USB drive "old" 0.045
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.160
And I unplug USB drive "old" 0.133
After features/support/hooks.rb:331 3.453
After features/support/hooks.rb:100 0.006
Tags: @product
1:22.515
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.047
And I start Tails from USB drive "old" with network unplugged and I login 50.233
Then Tails is running from USB drive "old" 0.272
And I create a persistent partition 23.003
And I take note of which tps features are available 0.661
Then a Tails persistence partition exists on USB drive "old" 0.477
And I shutdown Tails and wait for the computer to power off 7.817
After features/support/hooks.rb:331 0.349
After features/support/hooks.rb:100 0.007
Tags: @product
1:23.359
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 with persistence enabled 58.378
Then Tails is running from USB drive "old" 0.214
And all tps features are active 1.057
When I write some files expected to persist 1.159
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.184
And all persistence configuration files have safe access rights 0.428
And all persistent directories from the old Tails version have safe access rights 1.992
And I take note of which tps features are available 0.153
And I shutdown Tails and wait for the computer to power off 7.996
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.742
After features/support/hooks.rb:331 0.470
After features/support/hooks.rb:100 0.006
Tags: @product
2:8.749
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 without a persistent partition and stopped at Tails Greeter's login screen 7.805
And I log in to a new session 11.398
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.696
And I plug USB drive "to_upgrade" 2.231
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.061
Then the running Tails is installed on USB drive "to_upgrade" 15.267
And I unplug USB drive "to_upgrade" 0.136
And I unplug USB drive "__internal" 0.152
After features/support/hooks.rb:331 1.905
After features/support/hooks.rb:100 0.000
Tags: @product
1:7.339
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.047
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.015
Then all tps features from the old Tails version are active 0.917
And Tails is running from USB drive "to_upgrade" 0.223
And the boot device has safe access rights 2.249
And the expected persistent files created with the old Tails version are present in the filesystem 1.067
And all persistent directories from the old Tails version have safe access rights 1.818
After features/support/hooks.rb:331 0.863
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:28.077
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.078
And no SquashFS delta is installed 0.054
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.214
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.237
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.365
When the network is plugged 0.017
And Tor is ready 20.194
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.400
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.267
Given I shutdown Tails and wait for the computer to power off 19.782
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.098
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.210
And the file system changes introduced in version 6.2~testoverlayfs are present 0.264
And only the 6.2~testoverlayfs SquashFS delta is installed 0.055
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.164
# 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.224
When the network is plugged 0.021
And Tor is ready 20.036
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.369
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.808
Given I shutdown Tails and wait for the computer to power off 16.931
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.264
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.020
And the file system changes introduced in version 6.3~testoverlayfs are present 0.369
And only the 6.3~testoverlayfs SquashFS delta is installed 0.050
# 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.115
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.210
When the network is plugged 0.016
And Tor is ready 21.256
Then the Upgrader considers the system as up-to-date 0.101
# 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.378
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.443
After features/support/hooks.rb:331 0.868
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
24.390
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.272
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.211
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 0.039
But a current signing key is available on our website 0.000
When the network is plugged 0.022
And Tor is ready 16.443
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.349
After features/support/hooks.rb:331 0.825
After features/support/hooks.rb:100 0.000