Project Number Date
test_Tails_ISO_21619-tor-browser-15.0.16 6 16 Jun 2026, 09:53

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:27.069 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:9.916
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.015
Given a computer 0.261
And I create a 7200 MiB disk named "old" 0.031
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 13.999
When I start Tails from USB drive "old" with network unplugged 51.128
Then the boot device has safe access rights 2.757
And Tails is running from USB drive "old" 0.247
And there is no persistence partition on USB drive "old" 0.040
And process "udev-watchdog" is running 0.061
And udev-watchdog is monitoring the correct device 0.188
And I unplug USB drive "old" 0.150
After features/support/hooks.rb:339 1.312
After features/support/hooks.rb:108 0.019
Tags: @product
1:35.614
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.016
Given a computer 0.163
And I start Tails from USB drive "old" with network unplugged and I login 57.223
Then Tails is running from USB drive "old" 0.271
And I create a persistent partition 25.534
And I take note of which tps features are available 4.848
Then a Tails persistence partition exists on USB drive "old" 0.594
And I shutdown Tails and wait for the computer to power off 6.978
After features/support/hooks.rb:339 0.255
After features/support/hooks.rb:108 0.021
Tags: @product
1:42.439
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.016
Given a computer 0.161
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.835
Then Tails is running from USB drive "old" 0.218
And all tps features are active 5.787
When I write some files expected to persist 1.557
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.200
And all persistence configuration files have safe access rights 0.321
And all persistent directories from the old Tails version have safe access rights 1.993
And I take note of which tps features are available 4.145
And I shutdown Tails and wait for the computer to power off 8.452
# 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.764
After features/support/hooks.rb:339 0.469
After features/support/hooks.rb:108 0.028
Tags: @product
2:13.610
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.017
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.189
And I log in to a new session 13.396
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.822
And I plug USB drive "to_upgrade" 2.231
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.189
Then the running Tails is installed on USB drive "to_upgrade" 16.464
And I unplug USB drive "to_upgrade" 0.178
And I unplug USB drive "__internal" 0.138
After features/support/hooks.rb:339 0.847
After features/support/hooks.rb:108 0.000
Tags: @product
1:15.874
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.018
Given a computer 0.209
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.064
Then all tps features from the old Tails version are active 1.111
And Tails is running from USB drive "to_upgrade" 0.258
And the boot device has safe access rights 2.578
And the expected persistent files created with the old Tails version are present in the filesystem 1.580
And all persistent directories from the old Tails version have safe access rights 2.070
After features/support/hooks.rb:339 0.928
After features/support/hooks.rb:108 0.021
Tags: @product @automatic_upgrade
4:7.409
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.037
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.936
And no SquashFS delta is installed 0.094
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.249
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.260
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.389
When the network is plugged 0.016
And Tor is ready 13.912
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.071
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.291
Given I shutdown Tails and wait for the computer to power off 10.072
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.723
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 5.600
And the file system changes introduced in version 6.2~testoverlayfs are present 0.309
And only the 6.2~testoverlayfs SquashFS delta is installed 0.060
# 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.254
When the network is plugged 0.018
And Tor is ready 11.427
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.933
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.344
Given I shutdown Tails and wait for the computer to power off 8.383
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.079
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 5.673
And the file system changes introduced in version 6.3~testoverlayfs are present 0.444
And only the 6.3~testoverlayfs SquashFS delta is installed 0.060
# 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.139
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.249
When the network is plugged 0.020
And Tor is ready 9.840
Then the Upgrader considers the system as up-to-date 10.568
# 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.359
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.404
After features/support/hooks.rb:339 1.142
After features/support/hooks.rb:108 0.045
Tags: @product @automatic_upgrade
22.204
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.021
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.051
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.271
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.072
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 11.682
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.039
After features/support/hooks.rb:339 1.014
After features/support/hooks.rb:108 0.000