Project Number Date
test_Tails_ISO_21318-tor-browser-16.0 37 10 Jul 2026, 08:03

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:42.391 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:13.489
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.053
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" 12.966
When I start Tails from USB drive "old" with network unplugged 56.349
Then the boot device has safe access rights 2.435
And Tails is running from USB drive "old" 0.226
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.048
And udev-watchdog is monitoring the correct device 0.208
And I unplug USB drive "old" 0.136
After features/support/hooks.rb:339 3.627
After features/support/hooks.rb:108 0.056
Tags: @product
1:28.258
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.046
And I start Tails from USB drive "old" with network unplugged and I login 51.743
Then Tails is running from USB drive "old" 0.271
And I create a persistent partition 23.865
And I take note of which tps features are available 3.930
Then a Tails persistence partition exists on USB drive "old" 0.497
And I shutdown Tails and wait for the computer to power off 7.901
After features/support/hooks.rb:339 0.129
After features/support/hooks.rb:108 0.005
Tags: @product
1:33.166
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.048
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.343
Then Tails is running from USB drive "old" 0.227
And all tps features are active 4.790
When I write some files expected to persist 1.180
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.150
And all persistence configuration files have safe access rights 0.333
And all persistent directories from the old Tails version have safe access rights 1.859
And I take note of which tps features are available 3.680
And I shutdown Tails and wait for the computer to power off 7.952
# 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.599
After features/support/hooks.rb:339 0.194
After features/support/hooks.rb:108 0.005
Tags: @product
2:10.476
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.176
And I log in to a new session 12.443
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.964
And I plug USB drive "to_upgrade" 2.239
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.263
Then the running Tails is installed on USB drive "to_upgrade" 15.112
And I unplug USB drive "to_upgrade" 0.135
And I unplug USB drive "__internal" 0.141
After features/support/hooks.rb:339 2.555
After features/support/hooks.rb:108 0.000
Tags: @product
1:8.696
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.049
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.285
Then all tps features from the old Tails version are active 1.017
And Tails is running from USB drive "to_upgrade" 0.214
And the boot device has safe access rights 2.297
And the expected persistent files created with the old Tails version are present in the filesystem 0.991
And all persistent directories from the old Tails version have safe access rights 1.839
After features/support/hooks.rb:339 0.541
After features/support/hooks.rb:108 0.007
3:48.761
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.956
And no SquashFS delta is installed 0.069
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.320
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.087
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.233
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.381
When the network is plugged 0.017
And Tor is ready 12.171
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.993
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.543
Given I shutdown Tails and wait for the computer to power off 9.267
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.433
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.737
And the file system changes introduced in version 6.2~testoverlayfs are present 0.196
And only the 6.2~testoverlayfs SquashFS delta is installed 0.045
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.131
# 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.188
When the network is plugged 0.014
And Tor is ready 10.608
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.461
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.274
Given I shutdown Tails and wait for the computer to power off 8.169
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.963
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.916
And the file system changes introduced in version 6.3~testoverlayfs are present 0.356
And only the 6.3~testoverlayfs SquashFS delta is installed 0.034
# 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.150
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.215
When the network is plugged 0.020
And Tor is ready 9.634
Then the Upgrader considers the system as up-to-date 10.548
# 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.179
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.425
After features/support/hooks.rb:339 0.576
After features/support/hooks.rb:108 0.033
19.544
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.158
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.231
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the signing key used by the Upgrader is outdated 0.043
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 8.313
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.716
After features/support/hooks.rb:339 0.651
After features/support/hooks.rb:108 0.000