Project Number Date
test_Tails_ISO_21790-tor-0.4.9.13 2 25 Sep 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 13:21.089 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:11.438
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.086
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.407
When I start Tails from USB drive "old" with network unplugged 54.371
Then the boot device has safe access rights 1.984
And Tails is running from USB drive "old" 0.156
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.031
And udev-watchdog is monitoring the correct device 0.161
And I unplug USB drive "old" 0.152
After features/support/hooks.rb:339 3.621
After features/support/hooks.rb:108 0.053
Tags: @product
1:22.411
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.090
And I start Tails from USB drive "old" with network unplugged and I login 48.729
Then Tails is running from USB drive "old" 0.208
And I create a persistent partition 23.744
And I take note of which tps features are available 6.430
Then a Tails persistence partition exists on USB drive "old" 0.579
And I shutdown Tails and wait for the computer to power off 2.628
After features/support/hooks.rb:339 0.446
After features/support/hooks.rb:108 0.006
Tags: @product
1:33.168
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.091
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.170
Then Tails is running from USB drive "old" 0.199
And all tps features are active 7.720
When I write some files expected to persist 1.192
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.153
And all persistence configuration files have safe access rights 0.239
And all persistent directories from the old Tails version have safe access rights 1.637
And I take note of which tps features are available 6.754
And I shutdown Tails and wait for the computer to power off 2.531
# 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.476
After features/support/hooks.rb:339 0.169
After features/support/hooks.rb:108 0.006
Tags: @product
2:10.690
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.562
And I log in to a new session 10.974
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.663
And I plug USB drive "to_upgrade" 2.249
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.173
Then the running Tails is installed on USB drive "to_upgrade" 17.806
And I unplug USB drive "to_upgrade" 0.123
And I unplug USB drive "__internal" 0.138
After features/support/hooks.rb:339 0.628
After features/support/hooks.rb:108 0.000
Tags: @product
1:8.590
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.086
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.468
Then all tps features from the old Tails version are active 1.008
And Tails is running from USB drive "to_upgrade" 0.183
And the boot device has safe access rights 2.135
And the expected persistent files created with the old Tails version are present in the filesystem 1.137
And all persistent directories from the old Tails version have safe access rights 1.570
After features/support/hooks.rb:339 0.703
After features/support/hooks.rb:108 0.006
5:37.110
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.060
And no SquashFS delta is installed 0.072
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.225
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.172
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.287
When the network is plugged 0.031
And Tor is ready 13.011
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.460
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.813
Given I shutdown Tails and wait for the computer to power off 5.405
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.058
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 7.903
And the file system changes introduced in version 6.2~testoverlayfs are present 0.205
And only the 6.2~testoverlayfs SquashFS delta is installed 0.047
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.096
# 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.172
When the network is plugged 0.037
And Tor is ready 10.513
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2:6.043
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.725
Given I shutdown Tails and wait for the computer to power off 2.528
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.736
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 7.485
And the file system changes introduced in version 6.3~testoverlayfs are present 0.339
And only the 6.3~testoverlayfs SquashFS delta is installed 0.051
# 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.082
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.156
When the network is plugged 0.030
And Tor is ready 10.118
Then the Upgrader considers the system as up-to-date 0.067
# 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 3.671
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.445
After features/support/hooks.rb:339 0.815
After features/support/hooks.rb:108 0.010
17.678
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.646
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.270
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 0.044
But a current signing key is available on our website 0.000
When the network is plugged 0.022
And Tor is ready 8.171
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.463
After features/support/hooks.rb:339 1.086
After features/support/hooks.rb:108 0.000