Project Number Date
test_Tails_ISO_devel 4470 27 Jun 2026, 11:15

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:31.347 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
56.584
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.046
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 13.438
When I start Tails from USB drive "old" with network unplugged 39.287
Then the boot device has safe access rights 2.106
And Tails is running from USB drive "old" 0.252
And there is no persistence partition on USB drive "old" 0.056
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.188
And I unplug USB drive "old" 0.135
After features/support/hooks.rb:339 3.511
After features/support/hooks.rb:108 0.006
Tags: @product
1:29.936
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.043
And I start Tails from USB drive "old" with network unplugged and I login 52.046
Then Tails is running from USB drive "old" 0.264
And I create a persistent partition 24.777
And I take note of which tps features are available 4.168
Then a Tails persistence partition exists on USB drive "old" 0.628
And I shutdown Tails and wait for the computer to power off 8.006
After features/support/hooks.rb:339 0.446
After features/support/hooks.rb:108 0.007
Tags: @product
1:34.454
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.044
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.111
Then Tails is running from USB drive "old" 0.243
And all tps features are active 4.454
When I write some files expected to persist 1.171
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.143
And all persistence configuration files have safe access rights 0.277
And all persistent directories from the old Tails version have safe access rights 1.971
And I take note of which tps features are available 3.730
And I shutdown Tails and wait for the computer to power off 8.329
# 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.976
After features/support/hooks.rb:339 0.369
After features/support/hooks.rb:108 0.006
Tags: @product
2:9.780
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.202
And I log in to a new session 12.207
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.816
And I plug USB drive "to_upgrade" 2.227
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.274
Then the running Tails is installed on USB drive "to_upgrade" 14.785
And I unplug USB drive "to_upgrade" 0.136
And I unplug USB drive "__internal" 0.130
After features/support/hooks.rb:339 2.010
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.834
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.050
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.269
Then all tps features from the old Tails version are active 0.999
And Tails is running from USB drive "to_upgrade" 0.193
And the boot device has safe access rights 2.445
And the expected persistent files created with the old Tails version are present in the filesystem 1.019
And all persistent directories from the old Tails version have safe access rights 1.856
After features/support/hooks.rb:339 0.888
After features/support/hooks.rb:108 0.021
Tags: @product @automatic_upgrade
3:49.570
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.044
And no SquashFS delta is installed 0.063
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.245
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.237
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.365
When the network is plugged 0.013
And Tor is ready 12.305
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.994
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.371
Given I shutdown Tails and wait for the computer to power off 6.761
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.305
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 4.496
And the file system changes introduced in version 6.2~testoverlayfs are present 0.178
And only the 6.2~testoverlayfs SquashFS delta is installed 0.052
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.128
# 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.219
When the network is plugged 0.018
And Tor is ready 10.854
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.008
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.121
Given I shutdown Tails and wait for the computer to power off 8.237
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.970
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.655
And the file system changes introduced in version 6.3~testoverlayfs are present 0.369
And only the 6.3~testoverlayfs SquashFS delta is installed 0.052
# 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.141
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.196
When the network is plugged 0.013
And Tor is ready 11.080
Then the Upgrader considers the system as up-to-date 10.491
# 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.126
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.373
After features/support/hooks.rb:339 0.763
After features/support/hooks.rb:108 0.013
Tags: @product @automatic_upgrade
20.187
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.507
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.187
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the signing key used by the Upgrader is outdated 0.071
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 9.942
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.418
After features/support/hooks.rb:339 1.026
After features/support/hooks.rb:108 0.000