Project Number Date
test_Tails_ISO_stable 6486 01 Jul 2026, 15:58

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:27.358 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:9.085
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.058
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 14.184
When I start Tails from USB drive "old" with network unplugged 50.377
Then the boot device has safe access rights 2.765
And Tails is running from USB drive "old" 0.249
And there is no persistence partition on USB drive "old" 0.051
And process "udev-watchdog" is running 0.067
And udev-watchdog is monitoring the correct device 0.173
And I unplug USB drive "old" 0.132
After features/support/hooks.rb:339 1.708
After features/support/hooks.rb:108 0.005
Tags: @product
1:36.657
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.084
And I start Tails from USB drive "old" with network unplugged and I login 56.345
Then Tails is running from USB drive "old" 0.238
And I create a persistent partition 26.046
And I take note of which tps features are available 4.947
Then a Tails persistence partition exists on USB drive "old" 0.584
And I shutdown Tails and wait for the computer to power off 8.411
After features/support/hooks.rb:339 0.340
After features/support/hooks.rb:108 0.012
Tags: @product
1:45.695
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.010
Given a computer 0.066
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:9.933
Then Tails is running from USB drive "old" 0.224
And all tps features are active 5.060
When I write some files expected to persist 1.356
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.183
And all persistence configuration files have safe access rights 0.300
And all persistent directories from the old Tails version have safe access rights 1.990
And I take note of which tps features are available 4.811
And I shutdown Tails and wait for the computer to power off 8.435
# 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" 13.334
After features/support/hooks.rb:339 0.256
After features/support/hooks.rb:108 0.025
Tags: @product
2:14.610
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.650
And I log in to a new session 13.848
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.826
And I plug USB drive "to_upgrade" 2.281
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.625
Then the running Tails is installed on USB drive "to_upgrade" 17.089
And I unplug USB drive "to_upgrade" 0.147
And I unplug USB drive "__internal" 0.140
After features/support/hooks.rb:339 7.358
After features/support/hooks.rb:108 0.000
Tags: @product
1:15.827
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.074
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.888
Then all tps features from the old Tails version are active 0.997
And Tails is running from USB drive "to_upgrade" 0.284
And the boot device has safe access rights 2.613
And the expected persistent files created with the old Tails version are present in the filesystem 1.273
And all persistent directories from the old Tails version have safe access rights 2.696
After features/support/hooks.rb:339 1.008
After features/support/hooks.rb:108 0.007
Tags: @product @automatic_upgrade
4:4.476
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.062
And no SquashFS delta is installed 0.087
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.234
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.249
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.358
When the network is plugged 0.018
And Tor is ready 13.456
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.508
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.984
Given I shutdown Tails and wait for the computer to power off 7.122
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.558
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 6.016
And the file system changes introduced in version 6.2~testoverlayfs are present 0.273
And only the 6.2~testoverlayfs SquashFS delta is installed 0.059
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.170
# 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.344
When the network is plugged 0.042
And Tor is ready 10.299
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.154
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.973
Given I shutdown Tails and wait for the computer to power off 4.345
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.072
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 5.529
And the file system changes introduced in version 6.3~testoverlayfs are present 0.638
And only the 6.3~testoverlayfs SquashFS delta is installed 0.054
# 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.183
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.278
When the network is plugged 0.016
And Tor is ready 10.500
Then the Upgrader considers the system as up-to-date 10.606
# 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.823
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.400
After features/support/hooks.rb:339 1.053
After features/support/hooks.rb:108 0.015
Tags: @product @automatic_upgrade
21.004
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.449
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.205
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.081
But a current signing key is available on our website 0.000
When the network is plugged 0.019
And Tor is ready 10.488
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.700
After features/support/hooks.rb:339 0.771
After features/support/hooks.rb:108 0.000