Project Number Date
test_Tails_ISO_stable 6445 15 Jun 2026, 11:52

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:15.726 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.133
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.015
Given a computer 0.149
And I create a 7200 MiB disk named "old" 0.031
And I plug USB drive "old" 1.064
And I write an old version of the Tails USB image to disk "old" 13.816
When I start Tails from USB drive "old" with network unplugged 55.496
Then the boot device has safe access rights 2.874
And Tails is running from USB drive "old" 0.238
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.058
And udev-watchdog is monitoring the correct device 0.209
And I unplug USB drive "old" 0.137
After features/support/hooks.rb:339 3.515
After features/support/hooks.rb:108 0.018
Tags: @product
1:30.867
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.015
Given a computer 0.133
And I start Tails from USB drive "old" with network unplugged and I login 56.715
Then Tails is running from USB drive "old" 0.269
And I create a persistent partition 25.544
And I take note of which tps features are available 4.609
Then a Tails persistence partition exists on USB drive "old" 0.597
And I shutdown Tails and wait for the computer to power off 2.996
After features/support/hooks.rb:339 0.529
After features/support/hooks.rb:108 0.017
Tags: @product
1:37.497
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.041
Given a computer 0.200
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.813
Then Tails is running from USB drive "old" 0.243
And all tps features are active 4.830
When I write some files expected to persist 1.260
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.211
And all persistence configuration files have safe access rights 0.515
And all persistent directories from the old Tails version have safe access rights 2.059
And I take note of which tps features are available 4.200
And I shutdown Tails and wait for the computer to power off 4.518
# 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.642
After features/support/hooks.rb:339 0.352
After features/support/hooks.rb:108 0.017
Tags: @product
2:11.596
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.395
And I log in to a new session 12.993
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.710
And I plug USB drive "to_upgrade" 2.226
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.905
Then the running Tails is installed on USB drive "to_upgrade" 15.055
And I unplug USB drive "to_upgrade" 0.138
And I unplug USB drive "__internal" 0.171
After features/support/hooks.rb:339 2.041
After features/support/hooks.rb:108 0.000
Tags: @product
1:16.837
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.015
Given a computer 0.234
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:9.714
Then all tps features from the old Tails version are active 1.095
And Tails is running from USB drive "to_upgrade" 0.270
And the boot device has safe access rights 2.586
And the expected persistent files created with the old Tails version are present in the filesystem 1.065
And all persistent directories from the old Tails version have safe access rights 1.869
After features/support/hooks.rb:339 1.034
After features/support/hooks.rb:108 0.017
Tags: @product @automatic_upgrade
4:3.813
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.572
And no SquashFS delta is installed 0.069
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.234
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.225
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.448
When the network is plugged 0.014
And Tor is ready 12.654
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.634
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.598
Given I shutdown Tails and wait for the computer to power off 9.663
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.262
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 5.192
And the file system changes introduced in version 6.2~testoverlayfs are present 0.210
And only the 6.2~testoverlayfs SquashFS delta is installed 0.059
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.125
# 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.183
When the network is plugged 0.014
And Tor is ready 11.357
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.050
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.990
Given I shutdown Tails and wait for the computer to power off 8.242
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.083
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 5.301
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.040
# 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.127
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.216
When the network is plugged 0.017
And Tor is ready 11.377
Then the Upgrader considers the system as up-to-date 10.607
# 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.432
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.374
After features/support/hooks.rb:339 1.398
After features/support/hooks.rb:108 0.052
Tags: @product @automatic_upgrade
20.980
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.031
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.808
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.261
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.050
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 10.596
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.192
After features/support/hooks.rb:339 0.794
After features/support/hooks.rb:108 0.000