Project Number Date
test_Tails_ISO_stable 6634 03 Sep 2026, 16:46

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:27.773 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
57.613
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.104
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 14.231
When I start Tails from USB drive "old" with network unplugged 39.473
Then the boot device has safe access rights 2.192
And Tails is running from USB drive "old" 0.198
And there is no persistence partition on USB drive "old" 0.039
And process "udev-watchdog" is running 0.046
And udev-watchdog is monitoring the correct device 0.166
And I unplug USB drive "old" 0.118
After features/support/hooks.rb:339 1.594
After features/support/hooks.rb:108 0.006
Tags: @product
1:27.033
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.100
And I start Tails from USB drive "old" with network unplugged and I login 50.235
Then Tails is running from USB drive "old" 0.263
And I create a persistent partition 24.908
And I take note of which tps features are available 6.782
Then a Tails persistence partition exists on USB drive "old" 0.512
And I shutdown Tails and wait for the computer to power off 4.230
After features/support/hooks.rb:339 0.382
After features/support/hooks.rb:108 0.006
Tags: @product
1:40.190
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.083
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.572
Then Tails is running from USB drive "old" 0.291
And all tps features are active 7.378
When I write some files expected to persist 1.282
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.183
And all persistence configuration files have safe access rights 0.310
And all persistent directories from the old Tails version have safe access rights 1.793
And I take note of which tps features are available 7.242
And I shutdown Tails and wait for the computer to power off 3.891
# 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.159
After features/support/hooks.rb:339 0.160
After features/support/hooks.rb:108 0.007
Tags: @product
2:15.753
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.515
And I log in to a new session 12.362
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.904
And I plug USB drive "to_upgrade" 2.296
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.085
Then the running Tails is installed on USB drive "to_upgrade" 18.318
And I unplug USB drive "to_upgrade" 0.145
And I unplug USB drive "__internal" 0.123
After features/support/hooks.rb:339 1.687
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.458
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.091
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.231
Then all tps features from the old Tails version are active 1.274
And Tails is running from USB drive "to_upgrade" 0.279
And the boot device has safe access rights 2.567
And the expected persistent files created with the old Tails version are present in the filesystem 1.155
And all persistent directories from the old Tails version have safe access rights 1.857
After features/support/hooks.rb:339 0.720
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:35.274
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.391
And no SquashFS delta is installed 0.094
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.292
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.360
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.442
When the network is plugged 0.049
And Tor is ready 12.164
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.629
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.565
Given I shutdown Tails and wait for the computer to power off 5.691
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.301
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 8.726
And the file system changes introduced in version 6.2~testoverlayfs are present 0.232
And only the 6.2~testoverlayfs SquashFS delta is installed 0.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.092
# 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.180
When the network is plugged 0.037
And Tor is ready 10.422
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.024
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.045
Given I shutdown Tails and wait for the computer to power off 2.725
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.372
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.071
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.056
# 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.102
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.184
When the network is plugged 0.025
And Tor is ready 10.519
Then the Upgrader considers the system as up-to-date 0.074
# 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.497
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.395
After features/support/hooks.rb:339 0.578
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
19.450
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.296
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.256
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.075
But a current signing key is available on our website 0.000
When the network is plugged 0.025
And Tor is ready 9.747
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.012
After features/support/hooks.rb:339 0.752
After features/support/hooks.rb:108 0.000