Project Number Date
test_Tails_ISO_stable 6645 08 Sep 2026, 07:37

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:13.714 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:18.559
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.008
Given a computer 0.180
And I create a 7200 MiB disk named "old" 0.034
And I plug USB drive "old" 1.041
And I write an old version of the Tails USB image to disk "old" 14.012
When I start Tails from USB drive "old" with network unplugged 59.857
Then the boot device has safe access rights 2.467
And Tails is running from USB drive "old" 0.306
And there is no persistence partition on USB drive "old" 0.045
And process "udev-watchdog" is running 0.083
And udev-watchdog is monitoring the correct device 0.389
And I unplug USB drive "old" 0.139
After features/support/hooks.rb:339 1.143
After features/support/hooks.rb:108 0.009
Tags: @product
1:28.798
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.128
And I start Tails from USB drive "old" with network unplugged and I login 50.370
Then Tails is running from USB drive "old" 0.209
And I create a persistent partition 26.467
And I take note of which tps features are available 6.924
Then a Tails persistence partition exists on USB drive "old" 0.697
And I shutdown Tails and wait for the computer to power off 4.001
After features/support/hooks.rb:339 0.588
After features/support/hooks.rb:108 0.006
Tags: @product
1:39.456
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.084
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.563
Then Tails is running from USB drive "old" 0.218
And all tps features are active 8.155
When I write some files expected to persist 1.130
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.180
And all persistence configuration files have safe access rights 0.301
And all persistent directories from the old Tails version have safe access rights 1.970
And I take note of which tps features are available 6.601
And I shutdown Tails and wait for the computer to power off 3.855
# 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.395
After features/support/hooks.rb:339 0.346
After features/support/hooks.rb:108 0.006
Tags: @product
2:15.743
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.215
And I log in to a new session 12.256
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.684
And I plug USB drive "to_upgrade" 2.195
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.447
Then the running Tails is installed on USB drive "to_upgrade" 19.700
And I unplug USB drive "to_upgrade" 0.112
And I unplug USB drive "__internal" 0.130
After features/support/hooks.rb:339 1.745
After features/support/hooks.rb:108 0.000
Tags: @product
1:16.300
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.008
Given a computer 0.096
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.994
Then all tps features from the old Tails version are active 2.495
And Tails is running from USB drive "to_upgrade" 0.196
And the boot device has safe access rights 2.329
And the expected persistent files created with the old Tails version are present in the filesystem 1.770
And all persistent directories from the old Tails version have safe access rights 2.416
After features/support/hooks.rb:339 1.077
After features/support/hooks.rb:108 0.013
Tags: @product @automatic_upgrade
3:55.021
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.856
And no SquashFS delta is installed 0.073
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.277
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.260
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.341
When the network is plugged 0.846
And Tor is ready 14.406
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.069
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.650
Given I shutdown Tails and wait for the computer to power off 5.494
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.577
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 12.458
And the file system changes introduced in version 6.2~testoverlayfs are present 0.280
And only the 6.2~testoverlayfs SquashFS delta is installed 0.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.135
# 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.271
When the network is plugged 0.437
And Tor is ready 10.579
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.341
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.036
Given I shutdown Tails and wait for the computer to power off 4.080
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.291
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 8.524
And the file system changes introduced in version 6.3~testoverlayfs are present 0.304
And only the 6.3~testoverlayfs SquashFS delta is installed 0.057
# 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.095
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.243
When the network is plugged 0.028
And Tor is ready 10.585
Then the Upgrader considers the system as up-to-date 0.110
# 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.435
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.717
After features/support/hooks.rb:339 0.945
After features/support/hooks.rb:108 0.039
Tags: @product @automatic_upgrade
19.834
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.669
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.243
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the signing key used by the Upgrader is outdated 0.056
But a current signing key is available on our website 0.000
When the network is plugged 0.026
And Tor is ready 8.501
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.295
After features/support/hooks.rb:339 0.885
After features/support/hooks.rb:108 0.000