Project Number Date
test_Tails_ISO_21765-tor-browser-15.0.23 1 14 Sep 2026, 13:13

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:29.701 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:7.164
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.078
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 14.155
When I start Tails from USB drive "old" with network unplugged 48.640
Then the boot device has safe access rights 2.571
And Tails is running from USB drive "old" 0.261
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.044
And udev-watchdog is monitoring the correct device 0.200
And I unplug USB drive "old" 0.122
After features/support/hooks.rb:339 1.292
After features/support/hooks.rb:108 0.007
Tags: @product
1:27.935
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.100
And I start Tails from USB drive "old" with network unplugged and I login 50.644
Then Tails is running from USB drive "old" 0.242
And I create a persistent partition 25.233
And I take note of which tps features are available 6.943
Then a Tails persistence partition exists on USB drive "old" 0.618
And I shutdown Tails and wait for the computer to power off 4.152
After features/support/hooks.rb:339 0.462
After features/support/hooks.rb:108 0.005
Tags: @product
1:34.919
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.113
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.655
Then Tails is running from USB drive "old" 0.202
And all tps features are active 7.788
When I write some files expected to persist 1.199
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.169
And all persistence configuration files have safe access rights 0.249
And all persistent directories from the old Tails version have safe access rights 1.726
And I take note of which tps features are available 6.017
And I shutdown Tails and wait for the computer to power off 2.782
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 12.013
After features/support/hooks.rb:339 0.433
After features/support/hooks.rb:108 0.006
Tags: @product
2:12.918
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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 8.222
And I log in to a new session 12.434
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.703
And I plug USB drive "to_upgrade" 2.219
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.253
Then the running Tails is installed on USB drive "to_upgrade" 17.838
And I unplug USB drive "to_upgrade" 0.126
And I unplug USB drive "__internal" 0.120
After features/support/hooks.rb:339 1.915
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.849
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.099
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.014
Then all tps features from the old Tails version are active 0.930
And Tails is running from USB drive "to_upgrade" 0.214
And the boot device has safe access rights 1.941
And the expected persistent files created with the old Tails version are present in the filesystem 1.034
And all persistent directories from the old Tails version have safe access rights 1.614
After features/support/hooks.rb:339 0.965
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:36.236
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.962
And no SquashFS delta is installed 0.074
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.297
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.373
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.368
When the network is plugged 0.095
And Tor is ready 12.551
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.746
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.705
Given I shutdown Tails and wait for the computer to power off 5.456
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.611
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.342
And the file system changes introduced in version 6.2~testoverlayfs are present 0.191
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.147
# 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.182
When the network is plugged 0.049
And Tor is ready 10.311
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.476
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.488
Given I shutdown Tails and wait for the computer to power off 2.661
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.922
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.165
And the file system changes introduced in version 6.3~testoverlayfs are present 0.457
And only the 6.3~testoverlayfs SquashFS delta is installed 0.125
# 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.164
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.393
When the network is plugged 0.032
And Tor is ready 10.385
Then the Upgrader considers the system as up-to-date 0.077
# 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 2.964
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.321
After features/support/hooks.rb:339 0.497
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
18.677
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.913
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.217
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
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.025
And Tor is ready 8.459
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.938
After features/support/hooks.rb:339 1.008
After features/support/hooks.rb:108 0.000