Project Number Date
test_Tails_ISO_devel 4517 28 Jul 2026, 19:44

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:57.606 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:4.661
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.072
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 14.004
When I start Tails from USB drive "old" with network unplugged 45.792
Then the boot device has safe access rights 2.948
And Tails is running from USB drive "old" 0.299
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.056
And udev-watchdog is monitoring the correct device 0.248
And I unplug USB drive "old" 0.165
After features/support/hooks.rb:339 3.501
After features/support/hooks.rb:108 0.030
Tags: @product
1:29.801
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.047
And I start Tails from USB drive "old" with network unplugged and I login 55.073
Then Tails is running from USB drive "old" 0.275
And I create a persistent partition 25.350
And I take note of which tps features are available 4.498
Then a Tails persistence partition exists on USB drive "old" 0.551
And I shutdown Tails and wait for the computer to power off 4.005
After features/support/hooks.rb:339 0.611
After features/support/hooks.rb:108 0.005
Tags: @product
1:36.837
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.048
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.456
Then Tails is running from USB drive "old" 0.226
And all tps features are active 5.786
When I write some files expected to persist 1.346
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.166
And all persistence configuration files have safe access rights 0.352
And all persistent directories from the old Tails version have safe access rights 2.012
And I take note of which tps features are available 4.052
And I shutdown Tails and wait for the computer to power off 4.236
# 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.150
After features/support/hooks.rb:339 0.525
After features/support/hooks.rb:108 0.005
Tags: @product
2:13.010
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.027
And I log in to a new session 13.660
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.742
And I plug USB drive "to_upgrade" 2.226
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.133
Then the running Tails is installed on USB drive "to_upgrade" 15.913
And I unplug USB drive "to_upgrade" 0.126
And I unplug USB drive "__internal" 0.180
After features/support/hooks.rb:339 2.368
After features/support/hooks.rb:108 0.000
Tags: @product
1:16.528
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.081
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.965
Then all tps features from the old Tails version are active 0.969
And Tails is running from USB drive "to_upgrade" 0.225
And the boot device has safe access rights 3.089
And the expected persistent files created with the old Tails version are present in the filesystem 1.207
And all persistent directories from the old Tails version have safe access rights 1.989
After features/support/hooks.rb:339 0.814
After features/support/hooks.rb:108 0.022
Tags: @product @automatic_upgrade
3:55.289
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.889
And no SquashFS delta is installed 0.057
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.218
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.264
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.328
When the network is plugged 0.019
And Tor is ready 14.059
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.732
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.641
Given I shutdown Tails and wait for the computer to power off 5.728
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.467
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 5.146
And the file system changes introduced in version 6.2~testoverlayfs are present 0.282
And only the 6.2~testoverlayfs SquashFS delta is installed 0.046
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.149
# 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.171
When the network is plugged 0.017
And Tor is ready 11.081
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.822
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.964
Given I shutdown Tails and wait for the computer to power off 4.090
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.639
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 4.765
And the file system changes introduced in version 6.3~testoverlayfs are present 0.333
And only the 6.3~testoverlayfs SquashFS delta is installed 0.042
# 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.186
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.244
When the network is plugged 0.014
And Tor is ready 10.504
Then the Upgrader considers the system as up-to-date 10.571
# 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.304
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.426
After features/support/hooks.rb:339 0.744
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
21.477
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.440
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.240
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.042
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 10.265
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.428
After features/support/hooks.rb:339 0.824
After features/support/hooks.rb:108 0.000