Project Number Date
test_Tails_ISO_devel 4489 11 Jul 2026, 11:15

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:34.112 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:6.257
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.054
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.013
And I write an old version of the Tails USB image to disk "old" 13.258
When I start Tails from USB drive "old" with network unplugged 48.859
Then the boot device has safe access rights 2.457
And Tails is running from USB drive "old" 0.226
And there is no persistence partition on USB drive "old" 0.040
And process "udev-watchdog" is running 0.045
And udev-watchdog is monitoring the correct device 0.168
And I unplug USB drive "old" 0.125
After features/support/hooks.rb:339 1.193
After features/support/hooks.rb:108 0.005
Tags: @product
1:27.716
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.047
And I start Tails from USB drive "old" with network unplugged and I login 51.305
Then Tails is running from USB drive "old" 0.230
And I create a persistent partition 23.938
And I take note of which tps features are available 3.750
Then a Tails persistence partition exists on USB drive "old" 0.549
And I shutdown Tails and wait for the computer to power off 7.894
After features/support/hooks.rb:339 0.194
After features/support/hooks.rb:108 0.005
Tags: @product
1:33.901
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.076
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.994
Then Tails is running from USB drive "old" 0.264
And all tps features are active 4.476
When I write some files expected to persist 1.276
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.162
And all persistence configuration files have safe access rights 0.280
And all persistent directories from the old Tails version have safe access rights 1.801
And I take note of which tps features are available 3.871
And I shutdown Tails and wait for the computer to power off 7.911
# 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.786
After features/support/hooks.rb:339 0.434
After features/support/hooks.rb:108 0.006
Tags: @product
2:8.571
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.909
And I log in to a new session 11.626
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.767
And I plug USB drive "to_upgrade" 2.209
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.152
Then the running Tails is installed on USB drive "to_upgrade" 14.651
And I unplug USB drive "to_upgrade" 0.127
And I unplug USB drive "__internal" 0.128
After features/support/hooks.rb:339 1.768
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.594
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.048
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.027
Then all tps features from the old Tails version are active 0.933
And Tails is running from USB drive "to_upgrade" 0.227
And the boot device has safe access rights 2.416
And the expected persistent files created with the old Tails version are present in the filesystem 1.117
And all persistent directories from the old Tails version have safe access rights 1.823
After features/support/hooks.rb:339 0.679
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:48.888
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.210
And no SquashFS delta is installed 0.055
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.215
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.201
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.307
When the network is plugged 0.015
And Tor is ready 12.943
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.045
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.548
Given I shutdown Tails and wait for the computer to power off 10.549
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.619
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 4.665
And the file system changes introduced in version 6.2~testoverlayfs are present 0.238
And only the 6.2~testoverlayfs SquashFS delta is installed 0.048
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.135
# 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.184
When the network is plugged 0.012
And Tor is ready 10.733
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.534
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.878
Given I shutdown Tails and wait for the computer to power off 7.828
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.993
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 4.692
And the file system changes introduced in version 6.3~testoverlayfs are present 0.380
And only the 6.3~testoverlayfs SquashFS delta is installed 0.044
# 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.107
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.252
When the network is plugged 0.017
And Tor is ready 9.392
Then the Upgrader considers the system as up-to-date 10.512
# 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 4.076
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.373
After features/support/hooks.rb:339 0.997
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
19.181
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.230
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.043
And the signing key used by the Upgrader is outdated 0.049
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 8.581
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.054
After features/support/hooks.rb:339 1.050
After features/support/hooks.rb:108 0.000