Project Number Date
test_Tails_ISO_stable 6661 13 Sep 2026, 11:27

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 10:59.634 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.358
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.084
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.078
When I start Tails from USB drive "old" with network unplugged 54.732
Then the boot device has safe access rights 1.841
And Tails is running from USB drive "old" 0.261
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.031
And udev-watchdog is monitoring the correct device 0.126
And I unplug USB drive "old" 0.114
After features/support/hooks.rb:339 1.640
After features/support/hooks.rb:108 0.005
Tags: @product
1:18.004
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.076
And I start Tails from USB drive "old" with network unplugged and I login 46.425
Then Tails is running from USB drive "old" 0.193
And I create a persistent partition 22.216
And I take note of which tps features are available 5.979
Then a Tails persistence partition exists on USB drive "old" 0.526
And I shutdown Tails and wait for the computer to power off 2.586
After features/support/hooks.rb:339 0.310
After features/support/hooks.rb:108 0.006
Tags: @product
1:26.930
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.072
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.834
Then Tails is running from USB drive "old" 0.144
And all tps features are active 6.771
When I write some files expected to persist 1.039
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.136
And all persistence configuration files have safe access rights 0.240
And all persistent directories from the old Tails version have safe access rights 1.397
And I take note of which tps features are available 5.581
And I shutdown Tails and wait for the computer to power off 2.555
# 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.156
After features/support/hooks.rb:339 0.338
After features/support/hooks.rb:108 0.005
Tags: @product
2:9.252
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.028
And I log in to a new session 10.343
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.575
And I plug USB drive "to_upgrade" 2.192
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.571
Then the running Tails is installed on USB drive "to_upgrade" 17.288
And I unplug USB drive "to_upgrade" 0.133
And I unplug USB drive "__internal" 0.118
After features/support/hooks.rb:339 1.835
After features/support/hooks.rb:108 0.000
Tags: @product
1:5.063
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.080
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.363
Then all tps features from the old Tails version are active 1.058
And Tails is running from USB drive "to_upgrade" 0.234
And the boot device has safe access rights 2.032
And the expected persistent files created with the old Tails version are present in the filesystem 0.802
And all persistent directories from the old Tails version have safe access rights 1.490
After features/support/hooks.rb:339 0.626
After features/support/hooks.rb:108 0.005
3:31.100
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.918
And no SquashFS delta is installed 0.067
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.239
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.188
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.265
When the network is plugged 0.031
And Tor is ready 12.773
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.370
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.451
Given I shutdown Tails and wait for the computer to power off 5.228
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.984
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 7.161
And the file system changes introduced in version 6.2~testoverlayfs are present 0.199
And only the 6.2~testoverlayfs SquashFS delta is installed 0.055
# 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.199
When the network is plugged 0.032
And Tor is ready 10.309
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.848
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.693
Given I shutdown Tails and wait for the computer to power off 2.540
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.609
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.275
And the file system changes introduced in version 6.3~testoverlayfs are present 0.273
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.092
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.137
When the network is plugged 0.022
And Tor is ready 10.069
Then the Upgrader considers the system as up-to-date 10.397
# 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.113
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.328
After features/support/hooks.rb:339 0.768
After features/support/hooks.rb:108 0.008
17.924
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.876
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.246
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.035
And the signing key used by the Upgrader is outdated 0.040
But a current signing key is available on our website 0.000
When the network is plugged 0.035
And Tor is ready 7.758
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.931
After features/support/hooks.rb:339 0.756
After features/support/hooks.rb:108 0.000