Project Number Date
test_Tails_ISO_devel 4574 28 Aug 2026, 07:29

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 10:55.918 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.752
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.082
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 13.250
When I start Tails from USB drive "old" with network unplugged 48.148
Then the boot device has safe access rights 1.563
And Tails is running from USB drive "old" 0.174
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.242
And I unplug USB drive "old" 0.125
After features/support/hooks.rb:339 1.651
After features/support/hooks.rb:108 0.005
Tags: @product
1:16.322
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.093
And I start Tails from USB drive "old" with network unplugged and I login 44.855
Then Tails is running from USB drive "old" 0.179
And I create a persistent partition 22.216
And I take note of which tps features are available 5.989
Then a Tails persistence partition exists on USB drive "old" 0.448
And I shutdown Tails and wait for the computer to power off 2.539
After features/support/hooks.rb:339 0.519
After features/support/hooks.rb:108 0.005
Tags: @product
1:27.148
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.084
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.305
Then Tails is running from USB drive "old" 0.181
And all tps features are active 7.102
When I write some files expected to persist 0.925
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.134
And all persistence configuration files have safe access rights 0.195
And all persistent directories from the old Tails version have safe access rights 1.608
And I take note of which tps features are available 5.812
And I shutdown Tails and wait for the computer to power off 2.500
# 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.296
After features/support/hooks.rb:339 0.133
After features/support/hooks.rb:108 0.005
Tags: @product
2:10.665
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 7.885
And I log in to a new session 11.481
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.683
And I plug USB drive "to_upgrade" 2.201
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.562
Then the running Tails is installed on USB drive "to_upgrade" 17.611
And I unplug USB drive "to_upgrade" 0.119
And I unplug USB drive "__internal" 0.119
After features/support/hooks.rb:339 1.559
After features/support/hooks.rb:108 0.000
Tags: @product
1:4.644
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.082
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.851
Then all tps features from the old Tails version are active 0.918
And Tails is running from USB drive "to_upgrade" 0.204
And the boot device has safe access rights 2.075
And the expected persistent files created with the old Tails version are present in the filesystem 0.969
And all persistent directories from the old Tails version have safe access rights 1.543
After features/support/hooks.rb:339 0.569
After features/support/hooks.rb:108 0.011
3:33.035
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.951
And no SquashFS delta is installed 0.062
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.208
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.206
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.301
When the network is plugged 0.033
And Tor is ready 13.298
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.402
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.207
Given I shutdown Tails and wait for the computer to power off 6.486
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.391
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.630
And the file system changes introduced in version 6.2~testoverlayfs are present 0.179
And only the 6.2~testoverlayfs SquashFS delta is installed 0.052
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.093
# 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.185
When the network is plugged 0.027
And Tor is ready 9.950
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.423
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.463
Given I shutdown Tails and wait for the computer to power off 2.599
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.115
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 7.331
And the file system changes introduced in version 6.3~testoverlayfs are present 0.265
And only the 6.3~testoverlayfs SquashFS delta is installed 0.041
# 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.125
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.166
When the network is plugged 0.034
And Tor is ready 10.068
Then the Upgrader considers the system as up-to-date 10.409
# 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 2.949
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.321
After features/support/hooks.rb:339 0.769
After features/support/hooks.rb:108 0.010
19.349
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.789
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.222
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.034
And the signing key used by the Upgrader is outdated 0.046
But a current signing key is available on our website 0.000
When the network is plugged 0.035
And Tor is ready 10.351
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.869
After features/support/hooks.rb:339 0.795
After features/support/hooks.rb:108 0.000