Project Number Date
test_Tails_ISO_devel 4579 31 Aug 2026, 18:50

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:50.783 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.285
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.086
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.174
When I start Tails from USB drive "old" with network unplugged 42.600
Then the boot device has safe access rights 1.870
And Tails is running from USB drive "old" 0.190
And there is no persistence partition on USB drive "old" 0.039
And process "udev-watchdog" is running 0.041
And udev-watchdog is monitoring the correct device 0.130
And I unplug USB drive "old" 0.113
After features/support/hooks.rb:339 3.769
After features/support/hooks.rb:108 0.005
Tags: @product
1:18.215
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.078
And I start Tails from USB drive "old" with network unplugged and I login 46.676
Then Tails is running from USB drive "old" 0.202
And I create a persistent partition 22.073
And I take note of which tps features are available 5.952
Then a Tails persistence partition exists on USB drive "old" 0.600
And I shutdown Tails and wait for the computer to power off 2.630
After features/support/hooks.rb:339 0.615
After features/support/hooks.rb:108 0.005
Tags: @product
1:28.880
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 57.453
Then Tails is running from USB drive "old" 0.282
And all tps features are active 6.811
When I write some files expected to persist 0.971
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.165
And all persistence configuration files have safe access rights 0.281
And all persistent directories from the old Tails version have safe access rights 1.388
And I take note of which tps features are available 5.441
And I shutdown Tails and wait for the computer to power off 5.116
# 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.888
After features/support/hooks.rb:339 0.389
After features/support/hooks.rb:108 0.005
Tags: @product
2:8.495
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.967
And I log in to a new session 9.740
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.572
And I plug USB drive "to_upgrade" 2.171
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.391
Then the running Tails is installed on USB drive "to_upgrade" 17.431
And I unplug USB drive "to_upgrade" 0.108
And I unplug USB drive "__internal" 0.112
After features/support/hooks.rb:339 1.570
After features/support/hooks.rb:108 0.000
Tags: @product
1:5.212
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 "to_upgrade" with network unplugged and I login with persistence enabled 59.719
Then all tps features from the old Tails version are active 0.921
And Tails is running from USB drive "to_upgrade" 0.188
And the boot device has safe access rights 2.090
And the expected persistent files created with the old Tails version are present in the filesystem 0.837
And all persistent directories from the old Tails version have safe access rights 1.377
After features/support/hooks.rb:339 0.970
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:32.277
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 20.935
And no SquashFS delta is installed 0.076
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.180
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.028
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.169
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.249
When the network is plugged 0.026
And Tor is ready 11.582
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.969
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.672
Given I shutdown Tails and wait for the computer to power off 5.182
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.501
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.616
And the file system changes introduced in version 6.2~testoverlayfs are present 0.217
And only the 6.2~testoverlayfs SquashFS delta is installed 0.045
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.119
# 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.163
When the network is plugged 0.026
And Tor is ready 10.130
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.837
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.975
Given I shutdown Tails and wait for the computer to power off 2.598
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.869
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.613
And the file system changes introduced in version 6.3~testoverlayfs are present 0.336
And only the 6.3~testoverlayfs SquashFS delta is installed 0.039
# 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.119
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.178
When the network is plugged 0.032
And Tor is ready 9.973
Then the Upgrader considers the system as up-to-date 0.093
# 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.392
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.310
After features/support/hooks.rb:339 0.561
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
18.416
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.876
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 signing key used by the Upgrader is outdated 0.042
But a current signing key is available on our website 0.000
When the network is plugged 0.037
And Tor is ready 9.297
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.916
After features/support/hooks.rb:339 0.710
After features/support/hooks.rb:108 0.000