Project Number Date
test_Tails_ISO_devel 4264 04 Mar 2026, 09:15

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 15:4.923 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:26.787
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.183
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.078
And I write an old version of the Tails USB image to disk "old" 32.251
When I start Tails from USB drive "old" with network unplugged 49.371
Then the boot device has safe access rights 3.023
And Tails is running from USB drive "old" 0.315
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.061
And udev-watchdog is monitoring the correct device 0.221
And I unplug USB drive "old" 0.165
After features/support/hooks.rb:331 1.266
After features/support/hooks.rb:100 0.009
Tags: @product
1:42.843
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login 1:3.782
Then Tails is running from USB drive "old" 0.294
And I create a persistent partition 29.181
And I take note of which tps features are available 1.195
Then a Tails persistence partition exists on USB drive "old" 0.694
And I shutdown Tails and wait for the computer to power off 7.502
After features/support/hooks.rb:331 0.617
After features/support/hooks.rb:100 0.009
Tags: @product
1:51.121
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.166
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:17.422
Then Tails is running from USB drive "old" 0.312
And all tps features are active 1.948
When I write some files expected to persist 1.758
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.223
And all persistence configuration files have safe access rights 0.476
And all persistent directories from the old Tails version have safe access rights 2.279
And I take note of which tps features are available 0.517
And I shutdown Tails and wait for the computer to power off 7.551
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.465
After features/support/hooks.rb:331 0.283
After features/support/hooks.rb:100 0.008
Tags: @product
2:31.713
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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 11.636
And I log in to a new session 12.772
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.298
And I plug USB drive "to_upgrade" 2.466
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.784
Then the running Tails is installed on USB drive "to_upgrade" 20.367
And I unplug USB drive "to_upgrade" 0.177
And I unplug USB drive "__internal" 0.210
After features/support/hooks.rb:331 2.361
After features/support/hooks.rb:100 0.000
Tags: @product
1:26.660
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.217
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:18.195
Then all tps features from the old Tails version are active 1.388
And Tails is running from USB drive "to_upgrade" 0.303
And the boot device has safe access rights 3.038
And the expected persistent files created with the old Tails version are present in the filesystem 1.246
And all persistent directories from the old Tails version have safe access rights 2.271
After features/support/hooks.rb:331 0.712
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
5:32.273
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.627
And no SquashFS delta is installed 0.124
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.313
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.295
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.489
When the network is plugged 0.069
And Tor is ready 24.274
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.617
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.232
Given I shutdown Tails and wait for the computer to power off 20.543
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:30.107
Then Tails is running version 6.2~testoverlayfs 0.020
And all tps features are active 2.354
And the file system changes introduced in version 6.2~testoverlayfs are present 0.279
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.181
# 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.236
When the network is plugged 0.051
And Tor is ready 22.801
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.614
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.982
Given I shutdown Tails and wait for the computer to power off 18.488
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:29.875
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 2.345
And the file system changes introduced in version 6.3~testoverlayfs are present 0.485
And only the 6.3~testoverlayfs SquashFS delta is installed 0.074
# 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.163
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.272
When the network is plugged 0.053
And Tor is ready 22.853
Then the Upgrader considers the system as up-to-date 0.129
# 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 6.597
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.585
After features/support/hooks.rb:331 1.067
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
33.522
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.313
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.270
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.081
But a current signing key is available on our website 0.000
When the network is plugged 0.057
And Tor is ready 22.135
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.609
After features/support/hooks.rb:331 0.864
After features/support/hooks.rb:100 0.000