Project Number Date
test_Tails_ISO_devel 4427 02 Jun 2026, 11:09

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:59.260 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
59.216
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.048
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.599
When I start Tails from USB drive "old" with network unplugged 41.260
Then the boot device has safe access rights 2.627
And Tails is running from USB drive "old" 0.226
And there is no persistence partition on USB drive "old" 0.049
And process "udev-watchdog" is running 0.058
And udev-watchdog is monitoring the correct device 0.188
And I unplug USB drive "old" 0.131
After features/support/hooks.rb:335 1.277
After features/support/hooks.rb:104 0.006
Tags: @product
1:19.742
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.047
And I start Tails from USB drive "old" with network unplugged and I login 51.696
Then Tails is running from USB drive "old" 0.283
And I create a persistent partition 24.143
And I take note of which tps features are available 0.327
Then a Tails persistence partition exists on USB drive "old" 0.512
And I shutdown Tails and wait for the computer to power off 2.731
After features/support/hooks.rb:335 0.592
After features/support/hooks.rb:104 0.006
Tags: @product
1:24.904
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.054
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.432
Then Tails is running from USB drive "old" 0.229
And all tps features are active 1.002
When I write some files expected to persist 1.203
# 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.274
And all persistent directories from the old Tails version have safe access rights 1.678
And I take note of which tps features are available 0.142
And I shutdown Tails and wait for the computer to power off 7.959
# 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.771
After features/support/hooks.rb:335 0.474
After features/support/hooks.rb:104 0.007
Tags: @product
2:9.975
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 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.069
And I log in to a new session 12.065
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.682
And I plug USB drive "to_upgrade" 2.247
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.184
Then the running Tails is installed on USB drive "to_upgrade" 15.460
And I unplug USB drive "to_upgrade" 0.137
And I unplug USB drive "__internal" 0.127
After features/support/hooks.rb:335 1.851
After features/support/hooks.rb:104 0.000
Tags: @product
1:8.751
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.053
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.185
Then all tps features from the old Tails version are active 1.016
And Tails is running from USB drive "to_upgrade" 0.243
And the boot device has safe access rights 2.377
And the expected persistent files created with the old Tails version are present in the filesystem 1.093
And all persistent directories from the old Tails version have safe access rights 1.781
After features/support/hooks.rb:335 0.489
After features/support/hooks.rb:104 0.006
Tags: @product @automatic_upgrade
3:36.849
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.033
And no SquashFS delta is installed 0.082
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.219
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.217
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.400
When the network is plugged 0.015
And Tor is ready 13.227
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.480
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.526
Given I shutdown Tails and wait for the computer to power off 9.315
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.259
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.102
And the file system changes introduced in version 6.2~testoverlayfs are present 0.215
And only the 6.2~testoverlayfs SquashFS delta is installed 0.042
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.153
# 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.203
When the network is plugged 0.017
And Tor is ready 9.713
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.080
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.750
Given I shutdown Tails and wait for the computer to power off 8.310
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.003
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 1.064
And the file system changes introduced in version 6.3~testoverlayfs are present 0.379
And only the 6.3~testoverlayfs SquashFS delta is installed 0.046
# 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.159
When the network is plugged 0.016
And Tor is ready 10.648
Then the Upgrader considers the system as up-to-date 10.557
# 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.059
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.332
After features/support/hooks.rb:335 1.007
After features/support/hooks.rb:104 0.010
Tags: @product @automatic_upgrade
19.820
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.359
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.228
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.034
And the signing key used by the Upgrader is outdated 0.046
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 9.798
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.336
After features/support/hooks.rb:335 0.885
After features/support/hooks.rb:104 0.000