Project Number Date
test_Tails_ISO_21319-thunderbird-153 1 26 Oct 2026, 20:52

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:7.204 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:14.531
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.188
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.025
And I write an old version of the Tails USB image to disk "old" 13.650
When I start Tails from USB drive "old" with network unplugged 56.591
Then the boot device has safe access rights 2.381
And Tails is running from USB drive "old" 0.228
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.046
And udev-watchdog is monitoring the correct device 0.209
And I unplug USB drive "old" 0.120
After features/support/hooks.rb:339 3.593
After features/support/hooks.rb:108 0.094
Tags: @product
1:32.359
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.080
And I start Tails from USB drive "old" with network unplugged and I login 53.634
Then Tails is running from USB drive "old" 0.209
And I create a persistent partition 24.931
And I take note of which tps features are available 8.914
Then a Tails persistence partition exists on USB drive "old" 0.561
And I shutdown Tails and wait for the computer to power off 4.027
After features/support/hooks.rb:339 0.515
After features/support/hooks.rb:108 0.007
Tags: @product
1:40.093
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.112
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.792
Then Tails is running from USB drive "old" 0.207
And all tps features are active 7.833
When I write some files expected to persist 1.306
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.262
And all persistence configuration files have safe access rights 0.329
And all persistent directories from the old Tails version have safe access rights 1.933
And I take note of which tps features are available 6.905
And I shutdown Tails and wait for the computer to power off 3.934
# 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.475
After features/support/hooks.rb:339 0.246
After features/support/hooks.rb:108 0.006
Tags: @product
2:17.590
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.504
And I log in to a new session 12.868
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.840
And I plug USB drive "to_upgrade" 2.210
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.009
Then the running Tails is installed on USB drive "to_upgrade" 20.826
And I unplug USB drive "to_upgrade" 0.126
And I unplug USB drive "__internal" 0.203
After features/support/hooks.rb:339 1.855
After features/support/hooks.rb:108 0.000
Tags: @product
1:13.055
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.094
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.587
Then all tps features from the old Tails version are active 1.243
And Tails is running from USB drive "to_upgrade" 0.210
And the boot device has safe access rights 2.898
And the expected persistent files created with the old Tails version are present in the filesystem 1.105
And all persistent directories from the old Tails version have safe access rights 1.913
After features/support/hooks.rb:339 0.668
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:47.743
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.687
And no SquashFS delta is installed 0.111
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.210
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.241
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.352
When the network is plugged 0.042
And Tor is ready 13.163
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.454
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.502
Given I shutdown Tails and wait for the computer to power off 5.444
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.482
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.831
And the file system changes introduced in version 6.2~testoverlayfs are present 0.225
And only the 6.2~testoverlayfs SquashFS delta is installed 0.055
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.115
# 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.178
When the network is plugged 0.038
And Tor is ready 10.788
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.344
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.764
Given I shutdown Tails and wait for the computer to power off 4.019
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.167
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 8.719
And the file system changes introduced in version 6.3~testoverlayfs are present 0.396
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.118
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.200
When the network is plugged 0.038
And Tor is ready 10.617
Then the Upgrader considers the system as up-to-date 10.432
# 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.504
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.366
After features/support/hooks.rb:339 0.638
After features/support/hooks.rb:108 0.014
Tags: @product @automatic_upgrade
21.829
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 8.270
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.259
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the signing key used by the Upgrader is outdated 0.063
But a current signing key is available on our website 0.000
When the network is plugged 0.030
And Tor is ready 11.048
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.114
After features/support/hooks.rb:339 0.872
After features/support/hooks.rb:108 0.000