Project Number Date
test_Tails_ISO_stable 6550 31 Jul 2026, 11:49

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:52.209 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
52.948
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.073
And I create a 7200 MiB disk named "old" 0.018
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 12.886
When I start Tails from USB drive "old" with network unplugged 36.648
Then the boot device has safe access rights 1.769
And Tails is running from USB drive "old" 0.173
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.026
And udev-watchdog is monitoring the correct device 0.165
And I unplug USB drive "old" 0.119
After features/support/hooks.rb:339 3.586
After features/support/hooks.rb:108 0.005
Tags: @product
1:17.580
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.079
And I start Tails from USB drive "old" with network unplugged and I login 45.698
Then Tails is running from USB drive "old" 0.193
And I create a persistent partition 22.560
And I take note of which tps features are available 6.033
Then a Tails persistence partition exists on USB drive "old" 0.457
And I shutdown Tails and wait for the computer to power off 2.556
After features/support/hooks.rb:339 0.259
After features/support/hooks.rb:108 0.005
Tags: @product
1:27.995
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.083
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.270
Then Tails is running from USB drive "old" 0.213
And all tps features are active 7.117
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.164
And all persistence configuration files have safe access rights 0.282
And all persistent directories from the old Tails version have safe access rights 1.598
And I take note of which tps features are available 5.685
And I shutdown Tails and wait for the computer to power off 2.504
# 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.104
After features/support/hooks.rb:339 0.271
After features/support/hooks.rb:108 0.005
Tags: @product
2:10.438
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 8.024
And I log in to a new session 11.629
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.583
And I plug USB drive "to_upgrade" 2.223
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.826
Then the running Tails is installed on USB drive "to_upgrade" 16.933
And I unplug USB drive "to_upgrade" 0.112
And I unplug USB drive "__internal" 0.106
After features/support/hooks.rb:339 1.843
After features/support/hooks.rb:108 0.000
Tags: @product
1:3.371
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.074
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 57.839
Then all tps features from the old Tails version are active 0.957
And Tails is running from USB drive "to_upgrade" 0.184
And the boot device has safe access rights 1.832
And the expected persistent files created with the old Tails version are present in the filesystem 0.905
And all persistent directories from the old Tails version have safe access rights 1.578
After features/support/hooks.rb:339 0.779
After features/support/hooks.rb:108 0.005
3:41.205
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 21.035
And no SquashFS delta is installed 0.088
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.038
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.207
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.272
When the network is plugged 0.036
And Tor is ready 11.289
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.987
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.569
Given I shutdown Tails and wait for the computer to power off 5.206
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.130
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.239
And the file system changes introduced in version 6.2~testoverlayfs are present 0.171
And only the 6.2~testoverlayfs SquashFS delta is installed 0.039
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.090
# 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.157
When the network is plugged 0.023
And Tor is ready 10.147
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.023
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.320
Given I shutdown Tails and wait for the computer to power off 2.514
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.009
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 6.756
And the file system changes introduced in version 6.3~testoverlayfs are present 0.263
And only the 6.3~testoverlayfs SquashFS delta is installed 0.049
# 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.127
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.246
When the network is plugged 0.023
And Tor is ready 10.109
Then the Upgrader considers the system as up-to-date 10.463
# 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.092
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.269
After features/support/hooks.rb:339 0.619
After features/support/hooks.rb:108 0.051
18.670
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.744
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.207
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.031
And the signing key used by the Upgrader is outdated 0.039
But a current signing key is available on our website 0.000
When the network is plugged 0.023
And Tor is ready 8.214
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.408
After features/support/hooks.rb:339 0.997
After features/support/hooks.rb:108 0.000