Project Number Date
test_Tails_ISO_21318-tor-browser-16.0 51 23 Jul 2026, 14:38

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:45.950 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.946
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.050
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.849
When I start Tails from USB drive "old" with network unplugged 54.511
Then the boot device has safe access rights 2.808
And Tails is running from USB drive "old" 0.243
And there is no persistence partition on USB drive "old" 0.054
And process "udev-watchdog" is running 0.043
And udev-watchdog is monitoring the correct device 0.193
And I unplug USB drive "old" 0.165
After features/support/hooks.rb:339 3.600
After features/support/hooks.rb:108 0.005
Tags: @product
1:24.259
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.053
And I start Tails from USB drive "old" with network unplugged and I login 52.295
Then Tails is running from USB drive "old" 0.270
And I create a persistent partition 24.266
And I take note of which tps features are available 4.144
Then a Tails persistence partition exists on USB drive "old" 0.542
And I shutdown Tails and wait for the computer to power off 2.686
After features/support/hooks.rb:339 0.624
After features/support/hooks.rb:108 0.008
Tags: @product
1:33.934
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.053
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.731
Then Tails is running from USB drive "old" 0.230
And all tps features are active 5.745
When I write some files expected to persist 1.330
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.224
And all persistence configuration files have safe access rights 0.368
And all persistent directories from the old Tails version have safe access rights 1.905
And I take note of which tps features are available 3.818
And I shutdown Tails and wait for the computer to power off 4.061
# 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.465
After features/support/hooks.rb:339 0.418
After features/support/hooks.rb:108 0.012
Tags: @product
2:10.154
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.658
And I log in to a new session 12.748
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.738
And I plug USB drive "to_upgrade" 2.217
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.444
Then the running Tails is installed on USB drive "to_upgrade" 15.043
And I unplug USB drive "to_upgrade" 0.130
And I unplug USB drive "__internal" 0.173
After features/support/hooks.rb:339 2.426
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.225
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.055
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.591
Then all tps features from the old Tails version are active 1.118
And Tails is running from USB drive "to_upgrade" 0.207
And the boot device has safe access rights 2.380
And the expected persistent files created with the old Tails version are present in the filesystem 1.081
And all persistent directories from the old Tails version have safe access rights 1.790
After features/support/hooks.rb:339 0.477
After features/support/hooks.rb:108 0.051
Tags: @product @automatic_upgrade
3:52.654
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 with a persistent partition enabled and logged in 8.075
And no SquashFS delta is installed 0.074
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.317
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.369
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.416
When the network is plugged 0.014
And Tor is ready 12.280
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.515
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.929
Given I shutdown Tails and wait for the computer to power off 6.815
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.425
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 5.281
And the file system changes introduced in version 6.2~testoverlayfs are present 0.275
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.154
# 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.243
When the network is plugged 0.017
And Tor is ready 11.183
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.842
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.587
Given I shutdown Tails and wait for the computer to power off 4.183
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.255
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 5.268
And the file system changes introduced in version 6.3~testoverlayfs are present 0.342
And only the 6.3~testoverlayfs SquashFS delta is installed 0.045
# 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.145
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.280
When the network is plugged 0.057
And Tor is ready 9.785
Then the Upgrader considers the system as up-to-date 10.586
# 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.272
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.461
After features/support/hooks.rb:339 0.812
After features/support/hooks.rb:108 0.018
Tags: @product @automatic_upgrade
19.773
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.352
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.220
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.053
But a current signing key is available on our website 0.000
When the network is plugged 0.013
And Tor is ready 9.394
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.685
After features/support/hooks.rb:339 1.186
After features/support/hooks.rb:108 0.000