Project Number Date
test_Tails_ISO_21318-tor-browser-16.0 11 12 Jun 2026, 08:10

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:8.822 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:10.691
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.052
And I create a 7200 MiB disk named "old" 0.012
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.719
When I start Tails from USB drive "old" with network unplugged 52.520
Then the boot device has safe access rights 2.737
And Tails is running from USB drive "old" 0.217
And there is no persistence partition on USB drive "old" 0.048
And process "udev-watchdog" is running 0.042
And udev-watchdog is monitoring the correct device 0.179
And I unplug USB drive "old" 0.140
After features/support/hooks.rb:339 1.295
After features/support/hooks.rb:108 0.007
Tags: @product
1:34.282
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.061
And I start Tails from USB drive "old" with network unplugged and I login 54.786
Then Tails is running from USB drive "old" 0.248
And I create a persistent partition 25.987
And I take note of which tps features are available 4.550
Then a Tails persistence partition exists on USB drive "old" 0.649
And I shutdown Tails and wait for the computer to power off 7.996
After features/support/hooks.rb:339 0.583
After features/support/hooks.rb:108 0.007
Tags: @product
1:39.168
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.060
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.201
Then Tails is running from USB drive "old" 0.282
And all tps features are active 5.489
When I write some files expected to persist 1.475
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.201
And all persistence configuration files have safe access rights 0.372
And all persistent directories from the old Tails version have safe access rights 2.089
And I take note of which tps features are available 3.917
And I shutdown Tails and wait for the computer to power off 7.956
# 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.122
After features/support/hooks.rb:339 0.132
After features/support/hooks.rb:108 0.008
Tags: @product
2:10.372
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 without a persistent partition and stopped at Tails Greeter's login screen 7.780
And I log in to a new session 12.416
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.682
And I plug USB drive "to_upgrade" 2.213
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.809
Then the running Tails is installed on USB drive "to_upgrade" 15.128
And I unplug USB drive "to_upgrade" 0.159
And I unplug USB drive "__internal" 0.182
After features/support/hooks.rb:339 3.755
After features/support/hooks.rb:108 0.000
Tags: @product
1:14.869
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given a computer 0.061
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.708
Then all tps features from the old Tails version are active 1.000
And Tails is running from USB drive "to_upgrade" 0.228
And the boot device has safe access rights 2.460
And the expected persistent files created with the old Tails version are present in the filesystem 1.327
And all persistent directories from the old Tails version have safe access rights 2.082
After features/support/hooks.rb:339 0.927
After features/support/hooks.rb:108 0.013
3:58.915
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.672
And no SquashFS delta is installed 0.075
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.202
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.199
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.343
When the network is plugged 0.019
And Tor is ready 15.059
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.314
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.668
Given I shutdown Tails and wait for the computer to power off 6.925
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.338
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 4.737
And the file system changes introduced in version 6.2~testoverlayfs are present 0.256
And only the 6.2~testoverlayfs SquashFS delta is installed 0.078
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.142
# 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.179
When the network is plugged 0.021
And Tor is ready 11.724
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.383
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.925
Given I shutdown Tails and wait for the computer to power off 8.095
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.201
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.787
And the file system changes introduced in version 6.3~testoverlayfs are present 0.369
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.153
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.203
When the network is plugged 0.014
And Tor is ready 10.314
Then the Upgrader considers the system as up-to-date 10.547
# 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.450
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.394
After features/support/hooks.rb:339 1.003
After features/support/hooks.rb:108 0.013
20.522
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.946
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.256
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
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.021
And Tor is ready 9.458
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.737
After features/support/hooks.rb:339 0.743
After features/support/hooks.rb:108 0.000