Project Number Date
test_Tails_ISO_21318-tor-browser-16.0 18 19 Jun 2026, 08:12

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:36.757 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:0.169
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.018
Given a computer 0.131
And I create a 7200 MiB disk named "old" 0.024
And I plug USB drive "old" 1.042
And I write an old version of the Tails USB image to disk "old" 13.567
When I start Tails from USB drive "old" with network unplugged 42.532
Then the boot device has safe access rights 2.239
And Tails is running from USB drive "old" 0.217
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.042
And udev-watchdog is monitoring the correct device 0.198
And I unplug USB drive "old" 0.134
After features/support/hooks.rb:339 3.427
After features/support/hooks.rb:108 0.019
Tags: @product
1:30.423
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.015
Given a computer 0.131
And I start Tails from USB drive "old" with network unplugged and I login 52.198
Then Tails is running from USB drive "old" 0.240
And I create a persistent partition 24.794
And I take note of which tps features are available 4.043
Then a Tails persistence partition exists on USB drive "old" 0.600
And I shutdown Tails and wait for the computer to power off 8.414
After features/support/hooks.rb:339 0.475
After features/support/hooks.rb:108 0.021
Tags: @product
1:36.193
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.015
Given a computer 0.133
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.742
Then Tails is running from USB drive "old" 0.265
And all tps features are active 4.878
When I write some files expected to persist 1.189
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.146
And all persistence configuration files have safe access rights 0.268
And all persistent directories from the old Tails version have safe access rights 1.919
And I take note of which tps features are available 4.054
And I shutdown Tails and wait for the computer to power off 8.167
# 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.427
After features/support/hooks.rb:339 0.170
After features/support/hooks.rb:108 0.020
Tags: @product
2:9.715
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.016
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 7.929
And I log in to a new session 11.964
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.685
And I plug USB drive "to_upgrade" 2.237
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.485
Then the running Tails is installed on USB drive "to_upgrade" 15.118
And I unplug USB drive "to_upgrade" 0.138
And I unplug USB drive "__internal" 0.155
After features/support/hooks.rb:339 2.083
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.379
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.019
Given a computer 0.184
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.881
Then all tps features from the old Tails version are active 0.884
And Tails is running from USB drive "to_upgrade" 0.237
And the boot device has safe access rights 2.421
And the expected persistent files created with the old Tails version are present in the filesystem 1.074
And all persistent directories from the old Tails version have safe access rights 1.695
After features/support/hooks.rb:339 0.834
After features/support/hooks.rb:108 0.020
3:50.145
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.014
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.465
And no SquashFS delta is installed 0.083
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.208
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
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.348
When the network is plugged 0.017
And Tor is ready 12.038
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.578
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.565
Given I shutdown Tails and wait for the computer to power off 9.787
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.863
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 5.149
And the file system changes introduced in version 6.2~testoverlayfs are present 0.215
And only the 6.2~testoverlayfs SquashFS delta is installed 0.064
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.134
# 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.192
When the network is plugged 0.014
And Tor is ready 10.660
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.673
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.938
Given I shutdown Tails and wait for the computer to power off 4.484
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.986
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 4.700
And the file system changes introduced in version 6.3~testoverlayfs are present 0.331
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.116
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.180
When the network is plugged 0.014
And Tor is ready 9.950
Then the Upgrader considers the system as up-to-date 10.505
# 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.146
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.368
After features/support/hooks.rb:339 0.736
After features/support/hooks.rb:108 0.038
19.730
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.016
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.670
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.195
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 0.055
But a current signing key is available on our website 0.000
When the network is plugged 0.013
And Tor is ready 9.715
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.029
After features/support/hooks.rb:339 0.984
After features/support/hooks.rb:108 0.000