Project Number Date
test_Tails_ISO_devel 4469 26 Jun 2026, 11:20

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 12:6.891 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.515
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.097
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 14.068
When I start Tails from USB drive "old" with network unplugged 47.510
Then the boot device has safe access rights 2.844
And Tails is running from USB drive "old" 0.389
And there is no persistence partition on USB drive "old" 0.052
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.312
And I unplug USB drive "old" 0.153
After features/support/hooks.rb:339 3.624
After features/support/hooks.rb:108 0.005
Tags: @product
1:34.083
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.048
And I start Tails from USB drive "old" with network unplugged and I login 55.636
Then Tails is running from USB drive "old" 0.358
And I create a persistent partition 24.903
And I take note of which tps features are available 4.538
Then a Tails persistence partition exists on USB drive "old" 0.564
And I shutdown Tails and wait for the computer to power off 8.033
After features/support/hooks.rb:339 0.320
After features/support/hooks.rb:108 0.006
Tags: @product
1:41.084
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.047
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.964
Then Tails is running from USB drive "old" 0.262
And all tps features are active 5.173
When I write some files expected to persist 1.224
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.166
And all persistence configuration files have safe access rights 0.324
And all persistent directories from the old Tails version have safe access rights 1.842
And I take note of which tps features are available 3.982
And I shutdown Tails and wait for the computer to power off 8.563
# 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" 12.533
After features/support/hooks.rb:339 0.328
After features/support/hooks.rb:108 0.007
Tags: @product
2:12.915
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.552
And I log in to a new session 13.278
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.804
And I plug USB drive "to_upgrade" 2.236
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.839
Then the running Tails is installed on USB drive "to_upgrade" 15.923
And I unplug USB drive "to_upgrade" 0.146
And I unplug USB drive "__internal" 0.134
After features/support/hooks.rb:339 2.431
After features/support/hooks.rb:108 0.000
Tags: @product
1:16.673
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.049
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.915
Then all tps features from the old Tails version are active 1.122
And Tails is running from USB drive "to_upgrade" 0.285
And the boot device has safe access rights 2.857
And the expected persistent files created with the old Tails version are present in the filesystem 1.321
And all persistent directories from the old Tails version have safe access rights 2.120
After features/support/hooks.rb:339 0.591
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:55.937
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 8.382
And no SquashFS delta is installed 0.099
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.288
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.254
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.452
When the network is plugged 0.015
And Tor is ready 13.211
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.815
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.176
Given I shutdown Tails and wait for the computer to power off 6.885
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.339
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 5.778
And the file system changes introduced in version 6.2~testoverlayfs are present 0.251
And only the 6.2~testoverlayfs SquashFS delta is installed 0.080
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.136
# 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.242
When the network is plugged 0.023
And Tor is ready 9.813
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.958
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.769
Given I shutdown Tails and wait for the computer to power off 4.166
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.837
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 5.490
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.045
# 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.148
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.227
When the network is plugged 0.016
And Tor is ready 10.066
Then the Upgrader considers the system as up-to-date 10.671
# 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.423
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.445
After features/support/hooks.rb:339 1.039
After features/support/hooks.rb:108 0.016
Tags: @product @automatic_upgrade
19.681
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.263
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.254
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the signing key used by the Upgrader is outdated 0.057
But a current signing key is available on our website 0.000
When the network is plugged 0.021
And Tor is ready 10.030
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.005
After features/support/hooks.rb:339 1.084
After features/support/hooks.rb:108 0.000