Project Number Date
test_Tails_ISO_devel 4561 19 Aug 2026, 19:54

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:43.119 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:8.507
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.114
And I create a 7200 MiB disk named "old" 0.018
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 13.092
When I start Tails from USB drive "old" with network unplugged 51.789
Then the boot device has safe access rights 1.805
And Tails is running from USB drive "old" 0.251
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.083
And udev-watchdog is monitoring the correct device 0.166
And I unplug USB drive "old" 0.124
After features/support/hooks.rb:339 3.591
After features/support/hooks.rb:108 0.018
Tags: @product
1:19.860
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.081
And I start Tails from USB drive "old" with network unplugged and I login 45.643
Then Tails is running from USB drive "old" 0.193
And I create a persistent partition 23.138
And I take note of which tps features are available 6.397
Then a Tails persistence partition exists on USB drive "old" 0.454
And I shutdown Tails and wait for the computer to power off 3.951
After features/support/hooks.rb:339 0.443
After features/support/hooks.rb:108 0.005
Tags: @product
1:26.356
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.087
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.478
Then Tails is running from USB drive "old" 0.225
And all tps features are active 6.503
When I write some files expected to persist 0.954
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.095
And all persistence configuration files have safe access rights 0.240
And all persistent directories from the old Tails version have safe access rights 1.473
And I take note of which tps features are available 5.818
And I shutdown Tails and wait for the computer to power off 2.546
# 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.933
After features/support/hooks.rb:339 0.445
After features/support/hooks.rb:108 0.005
Tags: @product
2:8.949
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.976
And I log in to a new session 10.264
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.563
And I plug USB drive "to_upgrade" 2.217
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.501
Then the running Tails is installed on USB drive "to_upgrade" 17.180
And I unplug USB drive "to_upgrade" 0.126
And I unplug USB drive "__internal" 0.118
After features/support/hooks.rb:339 1.701
After features/support/hooks.rb:108 0.000
Tags: @product
1:4.352
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 "to_upgrade" with network unplugged and I login with persistence enabled 59.010
Then all tps features from the old Tails version are active 0.974
And Tails is running from USB drive "to_upgrade" 0.214
And the boot device has safe access rights 1.826
And the expected persistent files created with the old Tails version are present in the filesystem 0.889
And all persistent directories from the old Tails version have safe access rights 1.361
After features/support/hooks.rb:339 0.790
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
3:16.815
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.039
And no SquashFS delta is installed 0.053
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.227
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.033
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.199
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.343
When the network is plugged 0.031
And Tor is ready 12.726
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.384
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.191
Given I shutdown Tails and wait for the computer to power off 5.365
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.395
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.283
And the file system changes introduced in version 6.2~testoverlayfs are present 0.173
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.071
# 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.149
When the network is plugged 0.034
And Tor is ready 10.173
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.860
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.357
Given I shutdown Tails and wait for the computer to power off 2.544
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.087
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 6.851
And the file system changes introduced in version 6.3~testoverlayfs are present 0.302
And only the 6.3~testoverlayfs SquashFS delta is installed 0.037
# 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.101
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.154
When the network is plugged 0.033
And Tor is ready 10.012
Then the Upgrader considers the system as up-to-date 0.091
# 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.142
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.293
After features/support/hooks.rb:339 1.005
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
18.278
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.673
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.192
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.035
But a current signing key is available on our website 0.000
When the network is plugged 0.030
And Tor is ready 9.464
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.837
After features/support/hooks.rb:339 0.857
After features/support/hooks.rb:108 0.000