Project Number Date
test_Tails_ISO_21318-tor-browser-16.0 75 18 Aug 2026, 08:03

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:49.087 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:12.789
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.085
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.023
And I write an old version of the Tails USB image to disk "old" 13.186
When I start Tails from USB drive "old" with network unplugged 55.544
Then the boot device has safe access rights 2.208
And Tails is running from USB drive "old" 0.282
And there is no persistence partition on USB drive "old" 0.050
And process "udev-watchdog" is running 0.067
And udev-watchdog is monitoring the correct device 0.207
And I unplug USB drive "old" 0.114
After features/support/hooks.rb:339 3.759
After features/support/hooks.rb:108 0.011
Tags: @product
1:23.538
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.088
And I start Tails from USB drive "old" with network unplugged and I login 48.602
Then Tails is running from USB drive "old" 0.233
And I create a persistent partition 23.245
And I take note of which tps features are available 6.733
Then a Tails persistence partition exists on USB drive "old" 0.539
And I shutdown Tails and wait for the computer to power off 4.096
After features/support/hooks.rb:339 0.323
After features/support/hooks.rb:108 0.006
Tags: @product
1:32.138
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.087
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.850
Then Tails is running from USB drive "old" 0.200
And all tps features are active 7.459
When I write some files expected to persist 1.240
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.178
And all persistence configuration files have safe access rights 0.326
And all persistent directories from the old Tails version have safe access rights 1.654
And I take note of which tps features are available 6.197
And I shutdown Tails and wait for the computer to power off 2.508
# 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" 11.434
After features/support/hooks.rb:339 0.203
After features/support/hooks.rb:108 0.005
Tags: @product
2:14.243
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.516
And I log in to a new session 12.975
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.681
And I plug USB drive "to_upgrade" 2.267
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.925
Then the running Tails is installed on USB drive "to_upgrade" 18.624
And I unplug USB drive "to_upgrade" 0.114
And I unplug USB drive "__internal" 0.138
After features/support/hooks.rb:339 1.922
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.185
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.091
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.080
Then all tps features from the old Tails version are active 1.108
And Tails is running from USB drive "to_upgrade" 0.179
And the boot device has safe access rights 2.245
And the expected persistent files created with the old Tails version are present in the filesystem 0.871
And all persistent directories from the old Tails version have safe access rights 1.608
After features/support/hooks.rb:339 0.463
After features/support/hooks.rb:108 0.007
Tags: @product @automatic_upgrade
3:55.757
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 21.134
And no SquashFS delta is installed 0.053
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.176
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.210
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.290
When the network is plugged 0.023
And Tor is ready 12.780
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.191
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.302
Given I shutdown Tails and wait for the computer to power off 5.234
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.769
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.828
And the file system changes introduced in version 6.2~testoverlayfs are present 0.163
And only the 6.2~testoverlayfs SquashFS delta is installed 0.041
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.107
# 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.170
When the network is plugged 0.038
And Tor is ready 10.175
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.491
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.734
Given I shutdown Tails and wait for the computer to power off 4.033
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.711
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 7.941
And the file system changes introduced in version 6.3~testoverlayfs are present 0.313
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.108
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.211
When the network is plugged 0.037
And Tor is ready 10.029
Then the Upgrader considers the system as up-to-date 10.400
# 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 3.615
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.560
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
20.433
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.848
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.254
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
And the signing key used by the Upgrader is outdated 0.045
But a current signing key is available on our website 0.000
When the network is plugged 0.029
And Tor is ready 10.130
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.087
After features/support/hooks.rb:339 0.744
After features/support/hooks.rb:108 0.000