Project Number Date
test_Tails_ISO_21318-tor-browser-16.0 29 30 Jun 2026, 08:16

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:7.322 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.746
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.062
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 13.623
When I start Tails from USB drive "old" with network unplugged 55.537
Then the boot device has safe access rights 2.785
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.073
And udev-watchdog is monitoring the correct device 0.234
And I unplug USB drive "old" 0.131
After features/support/hooks.rb:339 1.605
After features/support/hooks.rb:108 0.007
Tags: @product
1:31.037
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 53.880
Then Tails is running from USB drive "old" 0.276
And I create a persistent partition 24.365
And I take note of which tps features are available 3.876
Then a Tails persistence partition exists on USB drive "old" 0.555
And I shutdown Tails and wait for the computer to power off 8.021
After features/support/hooks.rb:339 0.376
After features/support/hooks.rb:108 0.007
Tags: @product
1:36.034
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.007
Given a computer 0.070
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.223
Then Tails is running from USB drive "old" 0.297
And all tps features are active 4.697
When I write some files expected to persist 1.358
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.185
And all persistence configuration files have safe access rights 0.331
And all persistent directories from the old Tails version have safe access rights 2.012
And I take note of which tps features are available 4.478
And I shutdown Tails and wait for the computer to power off 4.113
# 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.265
After features/support/hooks.rb:339 0.404
After features/support/hooks.rb:108 0.012
Tags: @product
2:11.853
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 without a persistent partition and stopped at Tails Greeter's login screen 8.329
And I log in to a new session 12.511
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.043
And I plug USB drive "to_upgrade" 2.236
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.818
Then the running Tails is installed on USB drive "to_upgrade" 15.662
And I unplug USB drive "to_upgrade" 0.123
And I unplug USB drive "__internal" 0.128
After features/support/hooks.rb:339 3.786
After features/support/hooks.rb:108 0.000
Tags: @product
1:15.559
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.054
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.113
Then all tps features from the old Tails version are active 1.179
And Tails is running from USB drive "to_upgrade" 0.251
And the boot device has safe access rights 2.738
And the expected persistent files created with the old Tails version are present in the filesystem 1.321
And all persistent directories from the old Tails version have safe access rights 1.901
After features/support/hooks.rb:339 0.675
After features/support/hooks.rb:108 0.007
3:57.797
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.056
And no SquashFS delta is installed 0.095
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.409
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.434
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.371
When the network is plugged 0.033
And Tor is ready 13.910
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.325
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.289
Given I shutdown Tails and wait for the computer to power off 9.511
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.234
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 5.774
And the file system changes introduced in version 6.2~testoverlayfs are present 0.245
And only the 6.2~testoverlayfs SquashFS delta is installed 0.050
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.132
# 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.231
When the network is plugged 0.017
And Tor is ready 10.919
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.118
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.562
Given I shutdown Tails and wait for the computer to power off 6.781
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.277
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 5.877
And the file system changes introduced in version 6.3~testoverlayfs are present 0.449
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.152
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.199
When the network is plugged 0.028
And Tor is ready 9.742
Then the Upgrader considers the system as up-to-date 10.620
# 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.366
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.434
After features/support/hooks.rb:339 0.681
After features/support/hooks.rb:108 0.011
21.294
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.478
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.053
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.017
And Tor is ready 10.272
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.166
After features/support/hooks.rb:339 0.934
After features/support/hooks.rb:108 0.000