Project Number Date
test_Tails_ISO_21318-tor-browser-16.0 66 09 Aug 2026, 08:00

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.320 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:14.825
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.089
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.028
And I write an old version of the Tails USB image to disk "old" 13.740
When I start Tails from USB drive "old" with network unplugged 57.378
Then the boot device has safe access rights 1.971
And Tails is running from USB drive "old" 0.203
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.161
And I unplug USB drive "old" 0.128
After features/support/hooks.rb:339 3.778
After features/support/hooks.rb:108 0.062
Tags: @product
1:21.807
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.084
And I start Tails from USB drive "old" with network unplugged and I login 49.514
Then Tails is running from USB drive "old" 0.248
And I create a persistent partition 22.424
And I take note of which tps features are available 6.336
Then a Tails persistence partition exists on USB drive "old" 0.478
And I shutdown Tails and wait for the computer to power off 2.720
After features/support/hooks.rb:339 0.581
After features/support/hooks.rb:108 0.005
Tags: @product
1:34.229
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.091
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.014
Then Tails is running from USB drive "old" 0.274
And all tps features are active 7.754
When I write some files expected to persist 1.170
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.133
And all persistence configuration files have safe access rights 0.273
And all persistent directories from the old Tails version have safe access rights 1.563
And I take note of which tps features are available 6.171
And I shutdown Tails and wait for the computer to power off 2.570
# 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.211
After features/support/hooks.rb:339 0.575
After features/support/hooks.rb:108 0.005
Tags: @product
2:11.726
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.417
And I log in to a new session 11.472
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.568
And I plug USB drive "to_upgrade" 2.193
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.514
Then the running Tails is installed on USB drive "to_upgrade" 17.313
And I unplug USB drive "to_upgrade" 0.131
And I unplug USB drive "__internal" 0.115
After features/support/hooks.rb:339 0.612
After features/support/hooks.rb:108 0.000
Tags: @product
1:6.679
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.081
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.831
Then all tps features from the old Tails version are active 0.977
And Tails is running from USB drive "to_upgrade" 0.195
And the boot device has safe access rights 2.306
And the expected persistent files created with the old Tails version are present in the filesystem 0.787
And all persistent directories from the old Tails version have safe access rights 1.500
After features/support/hooks.rb:339 0.495
After features/support/hooks.rb:108 0.005
3:38.656
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.138
And no SquashFS delta is installed 0.054
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.229
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.177
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.374
When the network is plugged 0.038
And Tor is ready 11.494
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.151
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.679
Given I shutdown Tails and wait for the computer to power off 5.527
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.602
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.227
And the file system changes introduced in version 6.2~testoverlayfs are present 0.194
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.177
# 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.180
When the network is plugged 0.027
And Tor is ready 10.451
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.905
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.755
Given I shutdown Tails and wait for the computer to power off 2.839
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.079
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 7.995
And the file system changes introduced in version 6.3~testoverlayfs are present 0.363
And only the 6.3~testoverlayfs SquashFS delta is installed 0.030
# 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.102
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.162
When the network is plugged 0.027
And Tor is ready 11.592
Then the Upgrader considers the system as up-to-date 0.156
# 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.504
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.312
After features/support/hooks.rb:339 0.674
After features/support/hooks.rb:108 0.009
19.395
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.957
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.216
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.036
But a current signing key is available on our website 0.000
When the network is plugged 0.042
And Tor is ready 9.692
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.408
After features/support/hooks.rb:339 0.784
After features/support/hooks.rb:108 0.000