Project Number Date
test_Tails_ISO_21318-tor-browser-16.0 71 14 Aug 2026, 08:09

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:27.959 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:8.227
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.081
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.509
When I start Tails from USB drive "old" with network unplugged 51.041
Then the boot device has safe access rights 1.993
And Tails is running from USB drive "old" 0.199
And there is no persistence partition on USB drive "old" 0.051
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.139
And I unplug USB drive "old" 0.117
After features/support/hooks.rb:339 3.854
After features/support/hooks.rb:108 0.008
Tags: @product
1:22.888
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.131
And I start Tails from USB drive "old" with network unplugged and I login 48.488
Then Tails is running from USB drive "old" 0.232
And I create a persistent partition 23.281
And I take note of which tps features are available 5.951
Then a Tails persistence partition exists on USB drive "old" 0.498
And I shutdown Tails and wait for the computer to power off 4.303
After features/support/hooks.rb:339 0.530
After features/support/hooks.rb:108 0.010
Tags: @product
1:32.876
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.390
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.584
Then Tails is running from USB drive "old" 0.268
And all tps features are active 7.457
When I write some files expected to persist 1.065
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.131
And all persistence configuration files have safe access rights 0.267
And all persistent directories from the old Tails version have safe access rights 1.553
And I take note of which tps features are available 6.829
And I shutdown Tails and wait for the computer to power off 2.862
# 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.464
After features/support/hooks.rb:339 0.527
After features/support/hooks.rb:108 0.005
Tags: @product
2:13.206
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.370
And I log in to a new session 12.208
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.582
And I plug USB drive "to_upgrade" 2.302
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.410
Then the running Tails is installed on USB drive "to_upgrade" 18.107
And I unplug USB drive "to_upgrade" 0.114
And I unplug USB drive "__internal" 0.111
After features/support/hooks.rb:339 6.605
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.438
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.006
Given a computer 0.109
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.862
Then all tps features from the old Tails version are active 1.351
And Tails is running from USB drive "to_upgrade" 0.205
And the boot device has safe access rights 2.616
And the expected persistent files created with the old Tails version are present in the filesystem 1.244
And all persistent directories from the old Tails version have safe access rights 2.046
After features/support/hooks.rb:339 0.762
After features/support/hooks.rb:108 0.018
3:38.836
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 8.324
And no SquashFS delta is installed 0.062
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.211
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.187
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.361
When the network is plugged 0.027
And Tor is ready 12.617
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.966
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.248
Given I shutdown Tails and wait for the computer to power off 6.901
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.849
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.394
And the file system changes introduced in version 6.2~testoverlayfs are present 0.313
And only the 6.2~testoverlayfs SquashFS delta is installed 0.052
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.138
# 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.250
When the network is plugged 0.030
And Tor is ready 10.414
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.473
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.939
Given I shutdown Tails and wait for the computer to power off 4.291
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.926
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.916
And the file system changes introduced in version 6.3~testoverlayfs are present 0.347
And only the 6.3~testoverlayfs SquashFS delta is installed 0.036
# 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.109
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.149
When the network is plugged 0.040
And Tor is ready 10.664
Then the Upgrader considers the system as up-to-date 0.107
# 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.025
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.399
After features/support/hooks.rb:339 1.034
After features/support/hooks.rb:108 0.015
19.485
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.963
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.230
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the signing key used by the Upgrader is outdated 0.037
But a current signing key is available on our website 0.000
When the network is plugged 0.036
And Tor is ready 8.954
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.221
After features/support/hooks.rb:339 0.659
After features/support/hooks.rb:108 0.000