Project Number Date
test_Tails_ISO_devel 4547 13 Aug 2026, 18:52

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:40.305 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:18.368
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.099
And I create a 7200 MiB disk named "old" 0.029
And I plug USB drive "old" 1.028
And I write an old version of the Tails USB image to disk "old" 13.566
When I start Tails from USB drive "old" with network unplugged 1:0.265
Then the boot device has safe access rights 2.737
And Tails is running from USB drive "old" 0.240
And there is no persistence partition on USB drive "old" 0.045
And process "udev-watchdog" is running 0.045
And udev-watchdog is monitoring the correct device 0.197
And I unplug USB drive "old" 0.113
After features/support/hooks.rb:339 3.684
After features/support/hooks.rb:108 0.006
Tags: @product
1:24.114
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.008
Given a computer 0.122
And I start Tails from USB drive "old" with network unplugged and I login 48.903
Then Tails is running from USB drive "old" 0.196
And I create a persistent partition 23.353
And I take note of which tps features are available 6.661
Then a Tails persistence partition exists on USB drive "old" 0.603
And I shutdown Tails and wait for the computer to power off 4.272
After features/support/hooks.rb:339 0.307
After features/support/hooks.rb:108 0.006
Tags: @product
1:38.325
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.114
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.501
Then Tails is running from USB drive "old" 0.252
And all tps features are active 7.261
When I write some files expected to persist 1.265
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.231
And all persistence configuration files have safe access rights 0.302
And all persistent directories from the old Tails version have safe access rights 1.692
And I take note of which tps features are available 7.138
And I shutdown Tails and wait for the computer to power off 2.593
# 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.971
After features/support/hooks.rb:339 0.497
After features/support/hooks.rb:108 0.006
Tags: @product
2:16.474
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.796
And I log in to a new session 13.499
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.781
And I plug USB drive "to_upgrade" 2.199
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.920
Then the running Tails is installed on USB drive "to_upgrade" 19.047
And I unplug USB drive "to_upgrade" 0.119
And I unplug USB drive "__internal" 0.110
After features/support/hooks.rb:339 1.688
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.571
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.126
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.105
Then all tps features from the old Tails version are active 1.093
And Tails is running from USB drive "to_upgrade" 0.254
And the boot device has safe access rights 2.393
And the expected persistent files created with the old Tails version are present in the filesystem 0.957
And all persistent directories from the old Tails version have safe access rights 1.641
After features/support/hooks.rb:339 0.635
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:33.378
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.589
And no SquashFS delta is installed 0.051
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.221
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.223
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.317
When the network is plugged 0.035
And Tor is ready 12.850
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.655
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.656
Given I shutdown Tails and wait for the computer to power off 5.466
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.577
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.649
And the file system changes introduced in version 6.2~testoverlayfs are present 0.204
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.115
# 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.185
When the network is plugged 0.021
And Tor is ready 10.157
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.946
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.668
Given I shutdown Tails and wait for the computer to power off 4.242
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.249
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 8.162
And the file system changes introduced in version 6.3~testoverlayfs are present 0.389
And only the 6.3~testoverlayfs SquashFS delta is installed 0.056
# 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.131
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.177
When the network is plugged 0.040
And Tor is ready 10.635
Then the Upgrader considers the system as up-to-date 0.146
# 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.144
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.315
After features/support/hooks.rb:339 1.042
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
19.073
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.064
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.252
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.033
And the signing key used by the Upgrader is outdated 0.031
But a current signing key is available on our website 0.000
When the network is plugged 0.038
And Tor is ready 10.296
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.355
After features/support/hooks.rb:339 0.631
After features/support/hooks.rb:108 0.000