Project Number Date
test_Tails_ISO_stable 6604 24 Aug 2026, 12:53

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:37.876 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:0.612
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.107
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.535
When I start Tails from USB drive "old" with network unplugged 43.027
Then the boot device has safe access rights 2.299
And Tails is running from USB drive "old" 0.220
And there is no persistence partition on USB drive "old" 0.035
And process "udev-watchdog" is running 0.028
And udev-watchdog is monitoring the correct device 0.167
And I unplug USB drive "old" 0.147
After features/support/hooks.rb:339 1.449
After features/support/hooks.rb:108 0.006
Tags: @product
1:31.642
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 51.650
Then Tails is running from USB drive "old" 0.247
And I create a persistent partition 25.658
And I take note of which tps features are available 9.171
Then a Tails persistence partition exists on USB drive "old" 0.552
And I shutdown Tails and wait for the computer to power off 4.273
After features/support/hooks.rb:339 0.193
After features/support/hooks.rb:108 0.006
Tags: @product
1:42.644
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.722
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:7.516
Then Tails is running from USB drive "old" 0.306
And all tps features are active 8.097
When I write some files expected to persist 1.203
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.188
And all persistence configuration files have safe access rights 0.260
And all persistent directories from the old Tails version have safe access rights 1.764
And I take note of which tps features are available 6.512
And I shutdown Tails and wait for the computer to power off 4.196
# 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.875
After features/support/hooks.rb:339 0.246
After features/support/hooks.rb:108 0.006
Tags: @product
2:17.244
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.743
And I log in to a new session 13.617
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.675
And I plug USB drive "to_upgrade" 2.227
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.611
Then the running Tails is installed on USB drive "to_upgrade" 19.125
And I unplug USB drive "to_upgrade" 0.119
And I unplug USB drive "__internal" 0.123
After features/support/hooks.rb:339 1.731
After features/support/hooks.rb:108 0.000
Tags: @product
1:14.897
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.086
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.619
Then all tps features from the old Tails version are active 1.127
And Tails is running from USB drive "to_upgrade" 0.233
And the boot device has safe access rights 2.698
And the expected persistent files created with the old Tails version are present in the filesystem 1.192
And all persistent directories from the old Tails version have safe access rights 1.939
After features/support/hooks.rb:339 0.869
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:31.480
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.174
And no SquashFS delta is installed 0.066
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.209
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.035
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.215
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.305
When the network is plugged 0.035
And Tor is ready 13.335
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.941
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.575
Given I shutdown Tails and wait for the computer to power off 5.541
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.122
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.425
And the file system changes introduced in version 6.2~testoverlayfs are present 0.165
And only the 6.2~testoverlayfs SquashFS delta is installed 0.037
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.086
# 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.199
When the network is plugged 0.027
And Tor is ready 10.501
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.899
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.635
Given I shutdown Tails and wait for the computer to power off 2.613
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.342
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.804
And the file system changes introduced in version 6.3~testoverlayfs are present 0.431
And only the 6.3~testoverlayfs SquashFS delta is installed 0.034
# 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.142
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.182
When the network is plugged 0.025
And Tor is ready 10.324
Then the Upgrader considers the system as up-to-date 0.089
# 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.582
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.357
After features/support/hooks.rb:339 0.857
After features/support/hooks.rb:108 0.054
Tags: @product @automatic_upgrade
19.354
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.072
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.207
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 0.038
But a current signing key is available on our website 0.000
When the network is plugged 0.035
And Tor is ready 8.486
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.459
After features/support/hooks.rb:339 0.856
After features/support/hooks.rb:108 0.000