Project Number Date
test_Tails_ISO_stable 6485 01 Jul 2026, 11:38

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:46.277 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:18.737
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.049
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.244
When I start Tails from USB drive "old" with network unplugged 1:1.251
Then the boot device has safe access rights 2.529
And Tails is running from USB drive "old" 0.204
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.056
And udev-watchdog is monitoring the correct device 0.173
And I unplug USB drive "old" 0.164
After features/support/hooks.rb:339 3.813
After features/support/hooks.rb:108 0.030
Tags: @product
1:27.597
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.053
And I start Tails from USB drive "old" with network unplugged and I login 50.906
Then Tails is running from USB drive "old" 0.226
And I create a persistent partition 24.005
And I take note of which tps features are available 3.737
Then a Tails persistence partition exists on USB drive "old" 0.489
And I shutdown Tails and wait for the computer to power off 8.177
After features/support/hooks.rb:339 0.272
After features/support/hooks.rb:108 0.006
Tags: @product
1:33.907
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.046
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.241
Then Tails is running from USB drive "old" 0.250
And all tps features are active 4.389
When I write some files expected to persist 1.184
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.177
And all persistence configuration files have safe access rights 0.296
And all persistent directories from the old Tails version have safe access rights 1.836
And I take note of which tps features are available 3.825
And I shutdown Tails and wait for the computer to power off 7.906
# 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.752
After features/support/hooks.rb:339 0.448
After features/support/hooks.rb:108 0.006
Tags: @product
2:8.851
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 7.598
And I log in to a new session 11.673
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.739
And I plug USB drive "to_upgrade" 2.200
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.149
Then the running Tails is installed on USB drive "to_upgrade" 15.226
And I unplug USB drive "to_upgrade" 0.131
And I unplug USB drive "__internal" 0.132
After features/support/hooks.rb:339 2.057
After features/support/hooks.rb:108 0.000
Tags: @product
1:8.921
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.052
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.160
Then all tps features from the old Tails version are active 0.984
And Tails is running from USB drive "to_upgrade" 0.229
And the boot device has safe access rights 2.392
And the expected persistent files created with the old Tails version are present in the filesystem 1.147
And all persistent directories from the old Tails version have safe access rights 1.953
After features/support/hooks.rb:339 0.763
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:47.887
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.117
And no SquashFS delta is installed 0.058
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.197
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.212
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.376
When the network is plugged 0.019
And Tor is ready 12.871
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.367
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.173
Given I shutdown Tails and wait for the computer to power off 9.322
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.766
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.705
And the file system changes introduced in version 6.2~testoverlayfs are present 0.204
And only the 6.2~testoverlayfs SquashFS delta is installed 0.056
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.144
# 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.184
When the network is plugged 0.015
And Tor is ready 10.715
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.699
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.837
Given I shutdown Tails and wait for the computer to power off 8.113
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.058
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.787
And the file system changes introduced in version 6.3~testoverlayfs are present 0.432
And only the 6.3~testoverlayfs SquashFS delta is installed 0.042
# 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.170
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.220
When the network is plugged 0.047
And Tor is ready 10.842
Then the Upgrader considers the system as up-to-date 10.475
# 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.132
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.441
After features/support/hooks.rb:339 0.979
After features/support/hooks.rb:108 0.013
Tags: @product @automatic_upgrade
20.374
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.206
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.196
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.074
And the signing key used by the Upgrader is outdated 0.048
But a current signing key is available on our website 0.000
When the network is plugged 0.012
And Tor is ready 9.840
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.996
After features/support/hooks.rb:339 0.806
After features/support/hooks.rb:108 0.000