Project Number Date
test_Tails_ISO_stable 6544 29 Jul 2026, 19:25

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:0.021 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:4.327
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.067
And I create a 7200 MiB disk named "old" 0.011
And I plug USB drive "old" 1.027
And I write an old version of the Tails USB image to disk "old" 13.529
When I start Tails from USB drive "old" with network unplugged 46.033
Then the boot device has safe access rights 2.909
And Tails is running from USB drive "old" 0.285
And there is no persistence partition on USB drive "old" 0.081
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.196
And I unplug USB drive "old" 0.131
After features/support/hooks.rb:339 3.802
After features/support/hooks.rb:108 0.005
Tags: @product
1:28.513
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login 55.091
Then Tails is running from USB drive "old" 0.287
And I create a persistent partition 24.430
And I take note of which tps features are available 3.986
Then a Tails persistence partition exists on USB drive "old" 0.563
And I shutdown Tails and wait for the computer to power off 4.101
After features/support/hooks.rb:339 0.535
After features/support/hooks.rb:108 0.005
Tags: @product
1:36.986
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 with persistence enabled 1:7.422
Then Tails is running from USB drive "old" 0.230
And all tps features are active 4.836
When I write some files expected to persist 1.226
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.178
And all persistence configuration files have safe access rights 0.317
And all persistent directories from the old Tails version have safe access rights 2.134
And I take note of which tps features are available 4.256
And I shutdown Tails and wait for the computer to power off 4.241
# 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.058
After features/support/hooks.rb:339 0.391
After features/support/hooks.rb:108 0.030
Tags: @product
2:11.698
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.194
And I log in to a new session 12.935
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.091
And I plug USB drive "to_upgrade" 2.237
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.926
Then the running Tails is installed on USB drive "to_upgrade" 15.038
And I unplug USB drive "to_upgrade" 0.138
And I unplug USB drive "__internal" 0.137
After features/support/hooks.rb:339 2.263
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.775
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.048
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.489
Then all tps features from the old Tails version are active 1.040
And Tails is running from USB drive "to_upgrade" 0.215
And the boot device has safe access rights 2.915
And the expected persistent files created with the old Tails version are present in the filesystem 1.138
And all persistent directories from the old Tails version have safe access rights 1.927
After features/support/hooks.rb:339 0.584
After features/support/hooks.rb:108 0.016
4:0.187
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.094
And no SquashFS delta is installed 0.075
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.231
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.199
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.320
When the network is plugged 0.015
And Tor is ready 22.162
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.409
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.585
Given I shutdown Tails and wait for the computer to power off 6.844
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.852
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 5.155
And the file system changes introduced in version 6.2~testoverlayfs are present 0.219
And only the 6.2~testoverlayfs SquashFS delta is installed 0.047
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.148
# 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.220
When the network is plugged 0.028
And Tor is ready 9.809
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.190
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.541
Given I shutdown Tails and wait for the computer to power off 4.184
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.149
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.803
And the file system changes introduced in version 6.3~testoverlayfs are present 0.386
And only the 6.3~testoverlayfs SquashFS delta is installed 0.063
# 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.135
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.227
When the network is plugged 0.012
And Tor is ready 11.662
Then the Upgrader considers the system as up-to-date 10.539
# 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.435
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.376
After features/support/hooks.rb:339 0.725
After features/support/hooks.rb:108 0.014
25.531
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.524
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.225
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 0.049
But a current signing key is available on our website 0.000
When the network is plugged 0.013
And Tor is ready 15.199
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.468
After features/support/hooks.rb:339 0.711
After features/support/hooks.rb:108 0.000