Project Number Date
test_Tails_ISO_devel 4485 08 Jul 2026, 11:17

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 12:5.625 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:2.562
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.099
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.378
When I start Tails from USB drive "old" with network unplugged 44.184
Then the boot device has safe access rights 3.130
And Tails is running from USB drive "old" 0.277
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.048
And udev-watchdog is monitoring the correct device 0.205
And I unplug USB drive "old" 0.159
After features/support/hooks.rb:339 3.574
After features/support/hooks.rb:108 0.041
Tags: @product
1:32.011
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.103
And I start Tails from USB drive "old" with network unplugged and I login 53.333
Then Tails is running from USB drive "old" 0.261
And I create a persistent partition 25.399
And I take note of which tps features are available 4.135
Then a Tails persistence partition exists on USB drive "old" 0.539
And I shutdown Tails and wait for the computer to power off 8.238
After features/support/hooks.rb:339 0.439
After features/support/hooks.rb:108 0.007
Tags: @product
1:40.006
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.055
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.824
Then Tails is running from USB drive "old" 0.269
And all tps features are active 5.136
When I write some files expected to persist 1.215
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.120
And all persistence configuration files have safe access rights 0.319
And all persistent directories from the old Tails version have safe access rights 1.834
And I take note of which tps features are available 3.947
And I shutdown Tails and wait for the computer to power off 8.211
# 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" 12.073
After features/support/hooks.rb:339 0.287
After features/support/hooks.rb:108 0.007
Tags: @product
2:12.360
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.309
And I log in to a new session 12.622
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.997
And I plug USB drive "to_upgrade" 2.263
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.687
Then the running Tails is installed on USB drive "to_upgrade" 16.214
And I unplug USB drive "to_upgrade" 0.130
And I unplug USB drive "__internal" 0.134
After features/support/hooks.rb:339 1.936
After features/support/hooks.rb:108 0.000
Tags: @product
1:14.825
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.049
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.139
Then all tps features from the old Tails version are active 1.070
And Tails is running from USB drive "to_upgrade" 0.265
And the boot device has safe access rights 2.866
And the expected persistent files created with the old Tails version are present in the filesystem 1.329
And all persistent directories from the old Tails version have safe access rights 2.103
After features/support/hooks.rb:339 0.877
After features/support/hooks.rb:108 0.017
Tags: @product @automatic_upgrade
4:2.192
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.391
And no SquashFS delta is installed 0.069
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.254
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.235
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.363
When the network is plugged 0.014
And Tor is ready 13.698
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.457
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.717
Given I shutdown Tails and wait for the computer to power off 9.838
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.527
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 6.096
And the file system changes introduced in version 6.2~testoverlayfs are present 0.259
And only the 6.2~testoverlayfs SquashFS delta is installed 0.046
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.137
# 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.263
When the network is plugged 0.021
And Tor is ready 10.046
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.289
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.228
Given I shutdown Tails and wait for the computer to power off 8.445
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.327
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 5.561
And the file system changes introduced in version 6.3~testoverlayfs are present 0.444
And only the 6.3~testoverlayfs SquashFS delta is installed 0.080
# 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.138
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.233
When the network is plugged 0.019
And Tor is ready 9.705
Then the Upgrader considers the system as up-to-date 10.574
# 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 4.276
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.342
After features/support/hooks.rb:339 0.769
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
21.666
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.503
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.718
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.088
And the signing key used by the Upgrader is outdated 0.051
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 10.313
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.975
After features/support/hooks.rb:339 0.508
After features/support/hooks.rb:108 0.000