Project Number Date
test_Tails_ISO_devel 4534 07 Aug 2026, 11:19

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.718 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:11.120
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.096
And I create a 7200 MiB disk named "old" 0.023
And I plug USB drive "old" 1.029
And I write an old version of the Tails USB image to disk "old" 15.080
When I start Tails from USB drive "old" with network unplugged 51.441
Then the boot device has safe access rights 2.781
And Tails is running from USB drive "old" 0.230
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.048
And udev-watchdog is monitoring the correct device 0.195
And I unplug USB drive "old" 0.130
After features/support/hooks.rb:339 3.507
After features/support/hooks.rb:108 0.007
Tags: @product
1:25.080
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.101
And I start Tails from USB drive "old" with network unplugged and I login 50.114
Then Tails is running from USB drive "old" 0.253
And I create a persistent partition 24.408
And I take note of which tps features are available 7.087
Then a Tails persistence partition exists on USB drive "old" 0.500
And I shutdown Tails and wait for the computer to power off 2.615
After features/support/hooks.rb:339 0.299
After features/support/hooks.rb:108 0.006
Tags: @product
1:37.037
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.095
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.485
Then Tails is running from USB drive "old" 0.256
And all tps features are active 7.955
When I write some files expected to persist 1.254
# 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.303
And all persistent directories from the old Tails version have safe access rights 1.666
And I take note of which tps features are available 6.357
And I shutdown Tails and wait for the computer to power off 4.075
# 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.409
After features/support/hooks.rb:339 0.315
After features/support/hooks.rb:108 0.008
Tags: @product
2:15.086
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.660
And I log in to a new session 13.056
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.632
And I plug USB drive "to_upgrade" 2.217
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.270
Then the running Tails is installed on USB drive "to_upgrade" 18.012
And I unplug USB drive "to_upgrade" 0.122
And I unplug USB drive "__internal" 0.114
After features/support/hooks.rb:339 1.749
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.521
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.098
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.817
Then all tps features from the old Tails version are active 1.070
And Tails is running from USB drive "to_upgrade" 0.212
And the boot device has safe access rights 2.373
And the expected persistent files created with the old Tails version are present in the filesystem 1.085
And all persistent directories from the old Tails version have safe access rights 1.862
After features/support/hooks.rb:339 0.792
After features/support/hooks.rb:108 0.024
Tags: @product @automatic_upgrade
3:46.701
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.605
And no SquashFS delta is installed 0.123
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.345
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.247
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.295
When the network is plugged 0.023
And Tor is ready 13.051
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.316
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.393
Given I shutdown Tails and wait for the computer to power off 5.443
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.400
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.682
And the file system changes introduced in version 6.2~testoverlayfs are present 0.236
And only the 6.2~testoverlayfs SquashFS delta is installed 0.054
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.122
# 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.200
When the network is plugged 0.051
And Tor is ready 10.339
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.829
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.201
Given I shutdown Tails and wait for the computer to power off 4.087
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.788
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.229
And the file system changes introduced in version 6.3~testoverlayfs are present 0.319
And only the 6.3~testoverlayfs SquashFS delta is installed 0.048
# 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.121
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.194
When the network is plugged 0.032
And Tor is ready 10.420
Then the Upgrader considers the system as up-to-date 10.423
# 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 3.615
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.779
After features/support/hooks.rb:108 0.013
Tags: @product @automatic_upgrade
20.169
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 with a persistent partition enabled and logged in 8.018
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.243
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the signing key used by the Upgrader is outdated 0.044
But a current signing key is available on our website 0.000
When the network is plugged 0.028
And Tor is ready 10.648
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.119
After features/support/hooks.rb:339 1.053
After features/support/hooks.rb:108 0.000