Project Number Date
test_Tails_ISO_stable 6599 20 Aug 2026, 11: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 11:26.090 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:4.520
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given a computer 0.100
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.642
When I start Tails from USB drive "old" with network unplugged 46.983
Then the boot device has safe access rights 2.205
And Tails is running from USB drive "old" 0.214
And there is no persistence partition on USB drive "old" 0.037
And process "udev-watchdog" is running 0.034
And udev-watchdog is monitoring the correct device 0.154
And I unplug USB drive "old" 0.105
After features/support/hooks.rb:339 3.602
After features/support/hooks.rb:108 0.010
Tags: @product
1:24.377
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.095
And I start Tails from USB drive "old" with network unplugged and I login 48.968
Then Tails is running from USB drive "old" 0.326
And I create a persistent partition 23.663
And I take note of which tps features are available 6.701
Then a Tails persistence partition exists on USB drive "old" 0.466
And I shutdown Tails and wait for the computer to power off 4.155
After features/support/hooks.rb:339 0.505
After features/support/hooks.rb:108 0.039
Tags: @product
1:36.426
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.108
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.365
Then Tails is running from USB drive "old" 0.229
And all tps features are active 7.567
When I write some files expected to persist 1.066
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.138
And all persistence configuration files have safe access rights 0.305
And all persistent directories from the old Tails version have safe access rights 1.575
And I take note of which tps features are available 6.025
And I shutdown Tails and wait for the computer to power off 5.314
# 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.729
After features/support/hooks.rb:339 0.394
After features/support/hooks.rb:108 0.018
Tags: @product
2:13.097
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.817
And I log in to a new session 10.915
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.714
And I plug USB drive "to_upgrade" 2.210
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.121
Then the running Tails is installed on USB drive "to_upgrade" 19.070
And I unplug USB drive "to_upgrade" 0.132
And I unplug USB drive "__internal" 0.115
After features/support/hooks.rb:339 6.564
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.173
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.115
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.401
Then all tps features from the old Tails version are active 1.137
And Tails is running from USB drive "to_upgrade" 0.247
And the boot device has safe access rights 2.538
And the expected persistent files created with the old Tails version are present in the filesystem 1.057
And all persistent directories from the old Tails version have safe access rights 1.675
After features/support/hooks.rb:339 0.484
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:36.023
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 8.003
And no SquashFS delta is installed 0.061
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.210
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.265
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.613
When the network is plugged 0.027
And Tor is ready 13.445
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.873
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.584
Given I shutdown Tails and wait for the computer to power off 5.515
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.858
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 7.688
And the file system changes introduced in version 6.2~testoverlayfs are present 0.222
And only the 6.2~testoverlayfs SquashFS delta is installed 0.040
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.094
# 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.089
And Tor is ready 10.744
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.007
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.562
Given I shutdown Tails and wait for the computer to power off 4.188
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.984
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 8.272
And the file system changes introduced in version 6.3~testoverlayfs are present 0.311
And only the 6.3~testoverlayfs SquashFS delta is installed 0.051
# 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.114
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.145
When the network is plugged 0.033
And Tor is ready 10.491
Then the Upgrader considers the system as up-to-date 0.098
# 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.678
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.406
After features/support/hooks.rb:339 0.809
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
19.471
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 8.027
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.251
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the signing key used by the Upgrader is outdated 0.047
But a current signing key is available on our website 0.000
When the network is plugged 0.034
And Tor is ready 8.769
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.285
After features/support/hooks.rb:339 0.736
After features/support/hooks.rb:108 0.000