Project Number Date
test_Tails_ISO_stable 6610 27 Aug 2026, 07:26

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:48.147 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
59.827
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.093
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.023
And I write an old version of the Tails USB image to disk "old" 13.032
When I start Tails from USB drive "old" with network unplugged 43.111
Then the boot device has safe access rights 1.948
And Tails is running from USB drive "old" 0.205
And there is no persistence partition on USB drive "old" 0.032
And process "udev-watchdog" is running 0.027
And udev-watchdog is monitoring the correct device 0.164
And I unplug USB drive "old" 0.142
After features/support/hooks.rb:339 3.702
After features/support/hooks.rb:108 0.005
Tags: @product
1:17.361
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.088
And I start Tails from USB drive "old" with network unplugged and I login 45.134
Then Tails is running from USB drive "old" 0.189
And I create a persistent partition 22.479
And I take note of which tps features are available 6.447
Then a Tails persistence partition exists on USB drive "old" 0.449
And I shutdown Tails and wait for the computer to power off 2.574
After features/support/hooks.rb:339 0.463
After features/support/hooks.rb:108 0.005
Tags: @product
1:27.548
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.088
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.241
Then Tails is running from USB drive "old" 0.181
And all tps features are active 6.709
When I write some files expected to persist 1.030
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.129
And all persistence configuration files have safe access rights 0.242
And all persistent directories from the old Tails version have safe access rights 1.425
And I take note of which tps features are available 6.068
And I shutdown Tails and wait for the computer to power off 2.557
# 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" 10.873
After features/support/hooks.rb:339 0.255
After features/support/hooks.rb:108 0.005
Tags: @product
2:10.193
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.949
And I log in to a new session 11.510
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.577
And I plug USB drive "to_upgrade" 2.178
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.261
Then the running Tails is installed on USB drive "to_upgrade" 17.451
And I unplug USB drive "to_upgrade" 0.114
And I unplug USB drive "__internal" 0.150
After features/support/hooks.rb:339 6.744
After features/support/hooks.rb:108 0.000
Tags: @product
1:5.046
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.075
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.671
Then all tps features from the old Tails version are active 0.866
And Tails is running from USB drive "to_upgrade" 0.178
And the boot device has safe access rights 1.911
And the expected persistent files created with the old Tails version are present in the filesystem 0.925
And all persistent directories from the old Tails version have safe access rights 1.417
After features/support/hooks.rb:339 0.577
After features/support/hooks.rb:108 0.005
3:30.076
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.187
And no SquashFS delta is installed 0.062
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.198
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.024
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.184
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.282
When the network is plugged 0.031
And Tor is ready 11.278
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.592
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.313
Given I shutdown Tails and wait for the computer to power off 5.258
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.370
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 6.914
And the file system changes introduced in version 6.2~testoverlayfs are present 0.193
And only the 6.2~testoverlayfs SquashFS delta is installed 0.047
# 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.144
When the network is plugged 0.023
And Tor is ready 9.952
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.386
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.303
Given I shutdown Tails and wait for the computer to power off 3.894
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.086
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.590
And the file system changes introduced in version 6.3~testoverlayfs are present 0.246
And only the 6.3~testoverlayfs SquashFS delta is installed 0.047
# 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.152
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.160
When the network is plugged 0.032
And Tor is ready 10.065
Then the Upgrader considers the system as up-to-date 10.403
# 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.190
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.351
After features/support/hooks.rb:339 0.737
After features/support/hooks.rb:108 0.011
18.092
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 7.649
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.205
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
And the signing key used by the Upgrader is outdated 0.062
But a current signing key is available on our website 0.000
When the network is plugged 0.034
And Tor is ready 8.123
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.980
After features/support/hooks.rb:339 0.576
After features/support/hooks.rb:108 0.000