Project Number Date
test_Tails_ISO_devel 4536 09 Aug 2026, 11:14

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.917 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:16.599
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.083
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.023
And I write an old version of the Tails USB image to disk "old" 13.620
When I start Tails from USB drive "old" with network unplugged 59.487
Then the boot device has safe access rights 1.772
And Tails is running from USB drive "old" 0.206
And there is no persistence partition on USB drive "old" 0.037
And process "udev-watchdog" is running 0.031
And udev-watchdog is monitoring the correct device 0.197
And I unplug USB drive "old" 0.119
After features/support/hooks.rb:339 3.467
After features/support/hooks.rb:108 0.023
Tags: @product
1:22.617
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.077
And I start Tails from USB drive "old" with network unplugged and I login 48.650
Then Tails is running from USB drive "old" 0.253
And I create a persistent partition 22.952
And I take note of which tps features are available 6.128
Then a Tails persistence partition exists on USB drive "old" 0.578
And I shutdown Tails and wait for the computer to power off 3.975
After features/support/hooks.rb:339 0.250
After features/support/hooks.rb:108 0.009
Tags: @product
1:32.481
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given a computer 0.137
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.485
Then Tails is running from USB drive "old" 0.228
And all tps features are active 7.484
When I write some files expected to persist 0.983
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.152
And all persistence configuration files have safe access rights 0.251
And all persistent directories from the old Tails version have safe access rights 1.463
And I take note of which tps features are available 5.686
And I shutdown Tails and wait for the computer to power off 3.859
# 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.748
After features/support/hooks.rb:339 0.333
After features/support/hooks.rb:108 0.006
Tags: @product
2:13.527
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 8.493
And I log in to a new session 12.433
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.671
And I plug USB drive "to_upgrade" 2.231
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.537
Then the running Tails is installed on USB drive "to_upgrade" 17.909
And I unplug USB drive "to_upgrade" 0.135
And I unplug USB drive "__internal" 0.115
After features/support/hooks.rb:339 1.802
After features/support/hooks.rb:108 0.000
Tags: @product
1:7.763
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.080
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.327
Then all tps features from the old Tails version are active 1.084
And Tails is running from USB drive "to_upgrade" 0.229
And the boot device has safe access rights 2.226
And the expected persistent files created with the old Tails version are present in the filesystem 1.082
And all persistent directories from the old Tails version have safe access rights 1.733
After features/support/hooks.rb:339 0.895
After features/support/hooks.rb:108 0.041
Tags: @product @automatic_upgrade
3:43.537
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.623
And no SquashFS delta is installed 0.069
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.232
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.272
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.291
When the network is plugged 0.025
And Tor is ready 12.152
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 5.153
Given I shutdown Tails and wait for the computer to power off 5.364
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.415
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 8.317
And the file system changes introduced in version 6.2~testoverlayfs are present 0.221
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.143
# 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.187
When the network is plugged 0.033
And Tor is ready 10.435
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.016
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.339
Given I shutdown Tails and wait for the computer to power off 2.594
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.947
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.187
And the file system changes introduced in version 6.3~testoverlayfs are present 0.349
And only the 6.3~testoverlayfs SquashFS delta is installed 0.043
# 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.094
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.174
When the network is plugged 0.025
And Tor is ready 10.412
Then the Upgrader considers the system as up-to-date 10.534
# 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.773
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.382
After features/support/hooks.rb:339 0.860
After features/support/hooks.rb:108 0.051
Tags: @product @automatic_upgrade
18.389
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.840
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.210
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.023
And the signing key used by the Upgrader is outdated 0.044
But a current signing key is available on our website 0.000
When the network is plugged 0.035
And Tor is ready 7.918
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.316
After features/support/hooks.rb:339 0.789
After features/support/hooks.rb:108 0.000