Project Number Date
test_Tails_ISO_devel 4678 17 Oct 2026, 11:04

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:46.332 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:3.996
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.078
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.335
When I start Tails from USB drive "old" with network unplugged 47.098
Then the boot device has safe access rights 1.948
And Tails is running from USB drive "old" 0.166
And there is no persistence partition on USB drive "old" 0.030
And process "udev-watchdog" is running 0.046
And udev-watchdog is monitoring the correct device 0.131
And I unplug USB drive "old" 0.117
After features/support/hooks.rb:339 3.538
After features/support/hooks.rb:108 0.006
Tags: @product
1:18.814
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.082
And I start Tails from USB drive "old" with network unplugged and I login 46.202
Then Tails is running from USB drive "old" 0.210
And I create a persistent partition 22.943
And I take note of which tps features are available 6.334
Then a Tails persistence partition exists on USB drive "old" 0.503
And I shutdown Tails and wait for the computer to power off 2.537
After features/support/hooks.rb:339 0.505
After features/support/hooks.rb:108 0.005
Tags: @product
1:28.133
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.074
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.751
Then Tails is running from USB drive "old" 0.210
And all tps features are active 6.690
When I write some files expected to persist 1.032
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.154
And all persistence configuration files have safe access rights 0.271
And all persistent directories from the old Tails version have safe access rights 1.585
And I take note of which tps features are available 5.819
And I shutdown Tails and wait for the computer to power off 2.540
# 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.000
After features/support/hooks.rb:339 0.128
After features/support/hooks.rb:108 0.005
Tags: @product
2:11.345
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.316
And I log in to a new session 11.922
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.584
And I plug USB drive "to_upgrade" 2.242
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.446
Then the running Tails is installed on USB drive "to_upgrade" 17.585
And I unplug USB drive "to_upgrade" 0.123
And I unplug USB drive "__internal" 0.123
After features/support/hooks.rb:339 1.529
After features/support/hooks.rb:108 0.000
Tags: @product
1:4.104
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.075
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.466
Then all tps features from the old Tails version are active 1.064
And Tails is running from USB drive "to_upgrade" 0.201
And the boot device has safe access rights 2.197
And the expected persistent files created with the old Tails version are present in the filesystem 0.767
And all persistent directories from the old Tails version have safe access rights 1.331
After features/support/hooks.rb:339 0.551
After features/support/hooks.rb:108 0.005
3:21.145
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.163
And no SquashFS delta is installed 0.050
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.197
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.033
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.193
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.283
When the network is plugged 0.051
And Tor is ready 12.201
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.569
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.840
Given I shutdown Tails and wait for the computer to power off 5.233
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.700
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 7.413
And the file system changes introduced in version 6.2~testoverlayfs are present 0.153
And only the 6.2~testoverlayfs SquashFS delta is installed 0.038
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.130
# 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.195
When the network is plugged 0.024
And Tor is ready 10.453
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.310
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.583
Given I shutdown Tails and wait for the computer to power off 3.933
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.266
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 7.811
And the file system changes introduced in version 6.3~testoverlayfs are present 0.262
And only the 6.3~testoverlayfs SquashFS delta is installed 0.051
# 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.086
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.150
When the network is plugged 0.033
And Tor is ready 10.147
Then the Upgrader considers the system as up-to-date 0.080
# 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.083
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.401
After features/support/hooks.rb:339 0.691
After features/support/hooks.rb:108 0.082
18.792
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.772
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.192
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the signing key used by the Upgrader is outdated 0.030
But a current signing key is available on our website 0.000
When the network is plugged 0.036
And Tor is ready 9.360
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.364
After features/support/hooks.rb:339 0.938
After features/support/hooks.rb:108 0.000