Project Number Date
test_Tails_ISO_stable 6572 11 Aug 2026, 11:36

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:26.659 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:7.116
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.096
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.024
And I write an old version of the Tails USB image to disk "old" 13.736
When I start Tails from USB drive "old" with network unplugged 49.776
Then the boot device has safe access rights 1.893
And Tails is running from USB drive "old" 0.182
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.166
And I unplug USB drive "old" 0.120
After features/support/hooks.rb:339 3.406
After features/support/hooks.rb:108 0.005
Tags: @product
1:23.544
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.074
And I start Tails from USB drive "old" with network unplugged and I login 48.453
Then Tails is running from USB drive "old" 0.198
And I create a persistent partition 23.200
And I take note of which tps features are available 6.870
Then a Tails persistence partition exists on USB drive "old" 0.617
And I shutdown Tails and wait for the computer to power off 4.129
After features/support/hooks.rb:339 0.297
After features/support/hooks.rb:108 0.005
Tags: @product
1:30.683
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.105
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.445
Then Tails is running from USB drive "old" 0.209
And all tps features are active 7.224
When I write some files expected to persist 1.080
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.164
And all persistence configuration files have safe access rights 0.229
And all persistent directories from the old Tails version have safe access rights 1.689
And I take note of which tps features are available 6.615
And I shutdown Tails and wait for the computer to power off 2.634
# 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.284
After features/support/hooks.rb:339 0.137
After features/support/hooks.rb:108 0.005
Tags: @product
2:12.145
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.416
And I log in to a new session 11.275
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.589
And I plug USB drive "to_upgrade" 2.253
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.746
Then the running Tails is installed on USB drive "to_upgrade" 18.615
And I unplug USB drive "to_upgrade" 0.125
And I unplug USB drive "__internal" 0.122
After features/support/hooks.rb:339 0.586
After features/support/hooks.rb:108 0.000
Tags: @product
1:7.290
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.074
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.543
Then all tps features from the old Tails version are active 0.938
And Tails is running from USB drive "to_upgrade" 0.227
And the boot device has safe access rights 2.008
And the expected persistent files created with the old Tails version are present in the filesystem 0.982
And all persistent directories from the old Tails version have safe access rights 1.515
After features/support/hooks.rb:339 0.952
After features/support/hooks.rb:108 0.007
Tags: @product @automatic_upgrade
3:43.110
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.457
And no SquashFS delta is installed 0.119
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.235
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.033
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.248
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.403
When the network is plugged 0.028
And Tor is ready 12.560
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.125
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.964
Given I shutdown Tails and wait for the computer to power off 5.240
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.312
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.027
And the file system changes introduced in version 6.2~testoverlayfs are present 0.213
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.080
# 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.163
When the network is plugged 0.024
And Tor is ready 14.570
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.352
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.821
Given I shutdown Tails and wait for the computer to power off 4.171
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.217
Then Tails is running version 6.3~testoverlayfs 0.009
And all tps features are active 7.411
And the file system changes introduced in version 6.3~testoverlayfs are present 0.335
And only the 6.3~testoverlayfs SquashFS delta is installed 0.044
# 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.104
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.157
When the network is plugged 0.034
And Tor is ready 20.188
Then the Upgrader considers the system as up-to-date 0.104
# 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.955
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.316
After features/support/hooks.rb:339 0.799
After features/support/hooks.rb:108 0.038
Tags: @product @automatic_upgrade
22.768
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.009
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.206
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.027
And the signing key used by the Upgrader is outdated 0.034
But a current signing key is available on our website 0.000
When the network is plugged 0.029
And Tor is ready 12.788
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.672
After features/support/hooks.rb:339 0.938
After features/support/hooks.rb:108 0.000