Project Number Date
test_Tails_ISO_devel 4679 18 Oct 2026, 11:14

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:38.142 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:0.520
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.099
And I create a 7200 MiB disk named "old" 0.018
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.262
When I start Tails from USB drive "old" with network unplugged 43.608
Then the boot device has safe access rights 1.916
And Tails is running from USB drive "old" 0.207
And there is no persistence partition on USB drive "old" 0.053
And process "udev-watchdog" is running 0.046
And udev-watchdog is monitoring the correct device 0.170
And I unplug USB drive "old" 0.116
After features/support/hooks.rb:339 3.548
After features/support/hooks.rb:108 0.005
Tags: @product
1:18.625
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.095
And I start Tails from USB drive "old" with network unplugged and I login 45.534
Then Tails is running from USB drive "old" 0.217
And I create a persistent partition 23.410
And I take note of which tps features are available 6.227
Then a Tails persistence partition exists on USB drive "old" 0.495
And I shutdown Tails and wait for the computer to power off 2.643
After features/support/hooks.rb:339 0.227
After features/support/hooks.rb:108 0.005
Tags: @product
1:26.541
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.076
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.462
Then Tails is running from USB drive "old" 0.167
And all tps features are active 6.841
When I write some files expected to persist 0.864
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.099
And all persistence configuration files have safe access rights 0.222
And all persistent directories from the old Tails version have safe access rights 1.463
And I take note of which tps features are available 5.879
And I shutdown Tails and wait for the computer to power off 2.532
# 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" 10.931
After features/support/hooks.rb:339 0.265
After features/support/hooks.rb:108 0.005
Tags: @product
2:9.826
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.169
And I log in to a new session 10.787
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.644
And I plug USB drive "to_upgrade" 2.520
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.547
Then the running Tails is installed on USB drive "to_upgrade" 16.917
And I unplug USB drive "to_upgrade" 0.127
And I unplug USB drive "__internal" 0.111
After features/support/hooks.rb:339 1.728
After features/support/hooks.rb:108 0.000
Tags: @product
1:5.293
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.075
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.585
Then all tps features from the old Tails version are active 1.057
And Tails is running from USB drive "to_upgrade" 0.169
And the boot device has safe access rights 2.020
And the expected persistent files created with the old Tails version are present in the filesystem 0.952
And all persistent directories from the old Tails version have safe access rights 1.432
After features/support/hooks.rb:339 0.879
After features/support/hooks.rb:108 0.041
3:18.981
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 7.913
And no SquashFS delta is installed 0.053
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.255
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.035
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.167
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.283
When the network is plugged 0.027
And Tor is ready 12.953
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.315
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.683
Given I shutdown Tails and wait for the computer to power off 6.550
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.701
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.339
And the file system changes introduced in version 6.2~testoverlayfs are present 0.212
And only the 6.2~testoverlayfs SquashFS delta is installed 0.038
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.099
# 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.024
And Tor is ready 10.263
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.294
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.582
Given I shutdown Tails and wait for the computer to power off 2.560
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.175
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 6.876
And the file system changes introduced in version 6.3~testoverlayfs are present 0.272
And only the 6.3~testoverlayfs SquashFS delta is installed 0.057
# 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.071
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.163
When the network is plugged 0.036
And Tor is ready 10.218
Then the Upgrader considers the system as up-to-date 0.099
# 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.117
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.325
After features/support/hooks.rb:339 0.903
After features/support/hooks.rb:108 0.009
18.351
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 7.747
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.238
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the signing key used by the Upgrader is outdated 0.039
But a current signing key is available on our website 0.000
When the network is plugged 0.034
And Tor is ready 8.266
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.983
After features/support/hooks.rb:339 0.839
After features/support/hooks.rb:108 0.000