Project Number Date
test_Tails_ISO_stable 6298 14 Apr 2026, 19:47

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 13:0.178 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:16.576
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.063
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 14.180
When I start Tails from USB drive "old" with network unplugged 57.615
Then the boot device has safe access rights 2.945
And Tails is running from USB drive "old" 0.252
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.183
And I unplug USB drive "old" 0.219
After features/support/hooks.rb:331 3.519
After features/support/hooks.rb:100 0.006
Tags: @product
1:28.147
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.050
And I start Tails from USB drive "old" with network unplugged and I login 54.285
Then Tails is running from USB drive "old" 0.272
And I create a persistent partition 24.071
And I take note of which tps features are available 0.752
Then a Tails persistence partition exists on USB drive "old" 0.519
And I shutdown Tails and wait for the computer to power off 8.194
After features/support/hooks.rb:331 0.241
After features/support/hooks.rb:100 0.007
Tags: @product
1:32.101
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.059
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.204
Then Tails is running from USB drive "old" 0.267
And all tps features are active 1.211
When I write some files expected to persist 1.423
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.171
And all persistence configuration files have safe access rights 0.459
And all persistent directories from the old Tails version have safe access rights 2.033
And I take note of which tps features are available 0.165
And I shutdown Tails and wait for the computer to power off 8.010
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.094
After features/support/hooks.rb:331 0.254
After features/support/hooks.rb:100 0.007
Tags: @product
2:18.369
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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 7.625
And I log in to a new session 17.487
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.805
And I plug USB drive "to_upgrade" 2.255
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.098
Then the running Tails is installed on USB drive "to_upgrade" 16.818
And I unplug USB drive "to_upgrade" 0.137
And I unplug USB drive "__internal" 0.141
After features/support/hooks.rb:331 3.247
After features/support/hooks.rb:100 0.000
Tags: @product
1:12.607
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.062
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.047
Then all tps features from the old Tails version are active 0.943
And Tails is running from USB drive "to_upgrade" 0.343
And the boot device has safe access rights 3.090
And the expected persistent files created with the old Tails version are present in the filesystem 1.212
And all persistent directories from the old Tails version have safe access rights 1.907
After features/support/hooks.rb:331 0.625
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
4:45.839
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.935
And no SquashFS delta is installed 0.217
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.431
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.260
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.331
When the network is plugged 0.030
And Tor is ready 27.106
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.447
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.261
Given I shutdown Tails and wait for the computer to power off 21.324
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.813
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.209
And the file system changes introduced in version 6.2~testoverlayfs are present 0.265
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.156
# 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.176
When the network is plugged 0.016
And Tor is ready 21.120
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.374
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.975
Given I shutdown Tails and wait for the computer to power off 12.320
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.761
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 1.474
And the file system changes introduced in version 6.3~testoverlayfs are present 0.483
And only the 6.3~testoverlayfs SquashFS delta is installed 0.068
# 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.175
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.224
When the network is plugged 0.018
And Tor is ready 20.809
Then the Upgrader considers the system as up-to-date 0.137
# 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.330
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.472
After features/support/hooks.rb:331 0.716
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
26.535
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.679
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.274
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
And the signing key used by the Upgrader is outdated 0.066
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 17.996
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.466
After features/support/hooks.rb:331 0.859
After features/support/hooks.rb:100 0.000