Project Number Date
test_Tails_ISO_21318-tor-browser-16.0 24 25 Jun 2026, 08:05

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:31.197 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.666
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.074
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 13.002
When I start Tails from USB drive "old" with network unplugged 42.079
Then the boot device has safe access rights 2.772
And Tails is running from USB drive "old" 0.251
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.044
And udev-watchdog is monitoring the correct device 0.190
And I unplug USB drive "old" 0.187
After features/support/hooks.rb:339 3.436
After features/support/hooks.rb:108 0.005
Tags: @product
1:30.108
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.043
And I start Tails from USB drive "old" with network unplugged and I login 52.610
Then Tails is running from USB drive "old" 0.337
And I create a persistent partition 24.273
And I take note of which tps features are available 4.084
Then a Tails persistence partition exists on USB drive "old" 0.558
And I shutdown Tails and wait for the computer to power off 8.200
After features/support/hooks.rb:339 0.224
After features/support/hooks.rb:108 0.006
Tags: @product
1:34.640
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.045
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.652
Then Tails is running from USB drive "old" 0.221
And all tps features are active 4.797
When I write some files expected to persist 1.323
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.188
And all persistence configuration files have safe access rights 0.307
And all persistent directories from the old Tails version have safe access rights 1.943
And I take note of which tps features are available 3.623
And I shutdown Tails and wait for the computer to power off 7.828
# 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.709
After features/support/hooks.rb:339 0.185
After features/support/hooks.rb:108 0.006
Tags: @product
2:10.768
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.086
And I log in to a new session 13.907
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.778
And I plug USB drive "to_upgrade" 2.257
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.068
Then the running Tails is installed on USB drive "to_upgrade" 14.400
And I unplug USB drive "to_upgrade" 0.125
And I unplug USB drive "__internal" 0.143
After features/support/hooks.rb:339 3.942
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.202
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 "to_upgrade" with network unplugged and I login with persistence enabled 1:3.772
Then all tps features from the old Tails version are active 0.928
And Tails is running from USB drive "to_upgrade" 0.240
And the boot device has safe access rights 2.289
And the expected persistent files created with the old Tails version are present in the filesystem 1.095
And all persistent directories from the old Tails version have safe access rights 1.815
After features/support/hooks.rb:339 0.544
After features/support/hooks.rb:108 0.005
3:45.944
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 8.073
And no SquashFS delta is installed 0.063
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.260
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.225
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.322
When the network is plugged 0.037
And Tor is ready 11.931
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.462
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.301
Given I shutdown Tails and wait for the computer to power off 9.290
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.872
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 4.708
And the file system changes introduced in version 6.2~testoverlayfs are present 0.228
And only the 6.2~testoverlayfs SquashFS delta is installed 0.038
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.123
# 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.203
When the network is plugged 0.014
And Tor is ready 10.896
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.627
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.819
Given I shutdown Tails and wait for the computer to power off 4.012
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.006
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 5.739
And the file system changes introduced in version 6.3~testoverlayfs are present 0.349
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.137
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.205
When the network is plugged 0.013
And Tor is ready 9.856
Then the Upgrader considers the system as up-to-date 10.472
# 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.182
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.938
After features/support/hooks.rb:108 0.015
19.865
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.335
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.201
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.051
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 9.124
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.082
After features/support/hooks.rb:339 0.881
After features/support/hooks.rb:108 0.000