Project Number Date
test_Tails_ISO_stable 6576 13 Aug 2026, 11:34

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:8.919 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
58.614
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.088
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 12.860
When I start Tails from USB drive "old" with network unplugged 42.031
Then the boot device has safe access rights 1.931
And Tails is running from USB drive "old" 0.241
And there is no persistence partition on USB drive "old" 0.033
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.183
And I unplug USB drive "old" 0.147
After features/support/hooks.rb:339 3.455
After features/support/hooks.rb:108 0.004
Tags: @product
1:22.552
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.081
And I start Tails from USB drive "old" with network unplugged and I login 48.384
Then Tails is running from USB drive "old" 0.234
And I create a persistent partition 23.995
And I take note of which tps features are available 6.824
Then a Tails persistence partition exists on USB drive "old" 0.469
And I shutdown Tails and wait for the computer to power off 2.562
After features/support/hooks.rb:339 0.389
After features/support/hooks.rb:108 0.005
Tags: @product
1:31.903
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.075
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.861
Then Tails is running from USB drive "old" 0.216
And all tps features are active 6.821
When I write some files expected to persist 2.111
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.163
And all persistence configuration files have safe access rights 0.245
And all persistent directories from the old Tails version have safe access rights 1.996
And I take note of which tps features are available 6.483
And I shutdown Tails and wait for the computer to power off 2.551
# 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.376
After features/support/hooks.rb:339 0.477
After features/support/hooks.rb:108 0.006
Tags: @product
2:13.452
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.230
And I log in to a new session 12.118
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.817
And I plug USB drive "to_upgrade" 2.214
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.995
Then the running Tails is installed on USB drive "to_upgrade" 18.791
And I unplug USB drive "to_upgrade" 0.149
And I unplug USB drive "__internal" 0.134
After features/support/hooks.rb:339 1.636
After features/support/hooks.rb:108 0.000
Tags: @product
1:8.973
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.090
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.922
Then all tps features from the old Tails version are active 1.283
And Tails is running from USB drive "to_upgrade" 0.207
And the boot device has safe access rights 2.510
And the expected persistent files created with the old Tails version are present in the filesystem 1.095
And all persistent directories from the old Tails version have safe access rights 1.863
After features/support/hooks.rb:339 0.705
After features/support/hooks.rb:108 0.006
3:33.850
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.375
And no SquashFS delta is installed 0.075
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.281
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.208
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.354
When the network is plugged 0.034
And Tor is ready 12.434
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.134
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.377
Given I shutdown Tails and wait for the computer to power off 5.379
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.332
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 8.026
And the file system changes introduced in version 6.2~testoverlayfs are present 0.208
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.111
# 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.200
When the network is plugged 0.033
And Tor is ready 9.713
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.249
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.376
Given I shutdown Tails and wait for the computer to power off 2.576
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.204
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 8.411
And the file system changes introduced in version 6.3~testoverlayfs are present 0.337
And only the 6.3~testoverlayfs SquashFS delta is installed 0.052
# 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.151
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.202
When the network is plugged 0.040
And Tor is ready 10.445
Then the Upgrader considers the system as up-to-date 0.099
# 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.947
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.343
After features/support/hooks.rb:339 1.026
After features/support/hooks.rb:108 0.027
19.571
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.091
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.213
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.041
But a current signing key is available on our website 0.000
When the network is plugged 0.029
And Tor is ready 9.561
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.593
After features/support/hooks.rb:339 0.612
After features/support/hooks.rb:108 0.000