Project Number Date
test_Tails_ISO_devel 4303 30 Mar 2026, 07:38

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:55.630 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.817
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.079
And I create a 7200 MiB disk named "old" 0.011
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 13.070
When I start Tails from USB drive "old" with network unplugged 46.262
Then the boot device has safe access rights 2.649
And Tails is running from USB drive "old" 0.242
And there is no persistence partition on USB drive "old" 0.045
And process "udev-watchdog" is running 0.047
And udev-watchdog is monitoring the correct device 0.221
And I unplug USB drive "old" 0.169
After features/support/hooks.rb:331 3.764
After features/support/hooks.rb:100 0.006
Tags: @product
1:25.103
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.050
And I start Tails from USB drive "old" with network unplugged and I login 52.615
Then Tails is running from USB drive "old" 0.237
And I create a persistent partition 23.055
And I take note of which tps features are available 0.623
Then a Tails persistence partition exists on USB drive "old" 0.624
And I shutdown Tails and wait for the computer to power off 7.896
After features/support/hooks.rb:331 0.225
After features/support/hooks.rb:100 0.007
Tags: @product
1:20.416
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 59.371
Then Tails is running from USB drive "old" 0.260
And all tps features are active 1.120
When I write some files expected to persist 1.205
# 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.501
And all persistent directories from the old Tails version have safe access rights 1.661
And I take note of which tps features are available 0.186
And I shutdown Tails and wait for the computer to power off 4.090
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.778
After features/support/hooks.rb:331 0.413
After features/support/hooks.rb:100 0.007
Tags: @product
2:9.934
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.412
And I log in to a new session 11.918
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.791
And I plug USB drive "to_upgrade" 2.231
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.018
Then the running Tails is installed on USB drive "to_upgrade" 15.282
And I unplug USB drive "to_upgrade" 0.153
And I unplug USB drive "__internal" 0.126
After features/support/hooks.rb:331 2.360
After features/support/hooks.rb:100 0.000
Tags: @product
1:6.894
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.050
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.291
Then all tps features from the old Tails version are active 0.956
And Tails is running from USB drive "to_upgrade" 0.238
And the boot device has safe access rights 2.478
And the expected persistent files created with the old Tails version are present in the filesystem 1.042
And all persistent directories from the old Tails version have safe access rights 1.836
After features/support/hooks.rb:331 0.804
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
4:24.536
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.130
And no SquashFS delta is installed 0.064
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.262
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.080
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.224
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.367
When the network is plugged 0.015
And Tor is ready 19.194
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.413
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.185
Given I shutdown Tails and wait for the computer to power off 19.855
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.861
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.129
And the file system changes introduced in version 6.2~testoverlayfs are present 0.230
And only the 6.2~testoverlayfs SquashFS delta is installed 0.046
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.160
# 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.018
And Tor is ready 19.945
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.350
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.917
Given I shutdown Tails and wait for the computer to power off 13.113
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.441
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.056
And the file system changes introduced in version 6.3~testoverlayfs are present 0.326
And only the 6.3~testoverlayfs SquashFS delta is installed 0.043
# 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.131
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.170
When the network is plugged 0.019
And Tor is ready 20.866
Then the Upgrader considers the system as up-to-date 0.116
# 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.197
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.388
After features/support/hooks.rb:331 0.958
After features/support/hooks.rb:100 0.041
Tags: @product @automatic_upgrade
24.928
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 7.492
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.253
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
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.018
And Tor is ready 16.658
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.427
After features/support/hooks.rb:331 0.793
After features/support/hooks.rb:100 0.000