Project Number Date
test_Tails_ISO_21318-tor-browser-16.0 47 18 Jul 2026, 08:11

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:2.835 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
59.316
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.066
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.924
When I start Tails from USB drive "old" with network unplugged 40.893
Then the boot device has safe access rights 2.724
And Tails is running from USB drive "old" 0.226
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.046
And udev-watchdog is monitoring the correct device 0.216
And I unplug USB drive "old" 0.139
After features/support/hooks.rb:339 1.444
After features/support/hooks.rb:108 0.007
Tags: @product
1:28.418
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.064
And I start Tails from USB drive "old" with network unplugged and I login 53.991
Then Tails is running from USB drive "old" 0.265
And I create a persistent partition 26.108
And I take note of which tps features are available 4.621
Then a Tails persistence partition exists on USB drive "old" 0.540
And I shutdown Tails and wait for the computer to power off 2.826
After features/support/hooks.rb:339 0.576
After features/support/hooks.rb:108 0.008
Tags: @product
1:44.964
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.066
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:8.431
Then Tails is running from USB drive "old" 0.279
And all tps features are active 5.446
When I write some files expected to persist 1.683
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.168
And all persistence configuration files have safe access rights 0.385
And all persistent directories from the old Tails version have safe access rights 2.411
And I take note of which tps features are available 4.925
And I shutdown Tails and wait for the computer to power off 8.228
# 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.936
After features/support/hooks.rb:339 0.409
After features/support/hooks.rb:108 0.008
Tags: @product
2:10.818
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 7.292
And I log in to a new session 12.897
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.709
And I plug USB drive "to_upgrade" 2.215
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.704
Then the running Tails is installed on USB drive "to_upgrade" 15.709
And I unplug USB drive "to_upgrade" 0.146
And I unplug USB drive "__internal" 0.143
After features/support/hooks.rb:339 2.410
After features/support/hooks.rb:108 0.000
Tags: @product
1:16.689
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.068
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:9.035
Then all tps features from the old Tails version are active 1.049
And Tails is running from USB drive "to_upgrade" 0.299
And the boot device has safe access rights 2.694
And the expected persistent files created with the old Tails version are present in the filesystem 1.242
And all persistent directories from the old Tails version have safe access rights 2.300
After features/support/hooks.rb:339 0.573
After features/support/hooks.rb:108 0.047
4:2.554
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.033
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.882
And no SquashFS delta is installed 0.074
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.261
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.250
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.422
When the network is plugged 0.017
And Tor is ready 13.389
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.681
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.126
Given I shutdown Tails and wait for the computer to power off 5.518
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.722
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 5.130
And the file system changes introduced in version 6.2~testoverlayfs are present 0.198
And only the 6.2~testoverlayfs SquashFS delta is installed 0.047
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.139
# 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.190
When the network is plugged 0.018
And Tor is ready 11.842
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.920
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.060
Given I shutdown Tails and wait for the computer to power off 8.415
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.669
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 5.551
And the file system changes introduced in version 6.3~testoverlayfs are present 0.405
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.141
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.232
When the network is plugged 0.015
And Tor is ready 10.145
Then the Upgrader considers the system as up-to-date 10.622
# 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.841
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.514
After features/support/hooks.rb:339 0.996
After features/support/hooks.rb:108 0.023
20.073
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.771
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.223
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.040
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 10.040
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.931
After features/support/hooks.rb:339 0.746
After features/support/hooks.rb:108 0.000