Project Number Date
test_Tails_ISO_stable 6127 08 Feb 2026, 12:55

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:58.543 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
2:5.076
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.209
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.044
And I write an old version of the Tails USB image to disk "old" 40.616
When I start Tails from USB drive "old" with network unplugged 1:19.025
Then the boot device has safe access rights 3.273
And Tails is running from USB drive "old" 0.300
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.070
And udev-watchdog is monitoring the correct device 0.229
And I unplug USB drive "old" 0.199
After features/support/hooks.rb:331 1.674
After features/support/hooks.rb:100 0.009
Tags: @product
1:57.153
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.173
And I start Tails from USB drive "old" with network unplugged and I login 1:8.128
Then Tails is running from USB drive "old" 1.042
And I create a persistent partition 37.529
And I take note of which tps features are available 1.373
Then a Tails persistence partition exists on USB drive "old" 0.747
And I shutdown Tails and wait for the computer to power off 8.157
After features/support/hooks.rb:331 0.433
After features/support/hooks.rb:100 0.008
Tags: @product
1:56.882
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.165
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:21.525
Then Tails is running from USB drive "old" 0.302
And all tps features are active 2.066
When I write some files expected to persist 1.645
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.173
And all persistence configuration files have safe access rights 0.335
And all persistent directories from the old Tails version have safe access rights 3.128
And I take note of which tps features are available 0.566
And I shutdown Tails and wait for the computer to power off 7.849
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.122
After features/support/hooks.rb:331 0.592
After features/support/hooks.rb:100 0.009
Tags: @product
2:57.146
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 14.075
And I log in to a new session 14.441
And I clone USB drive "old" to a new USB drive "to_upgrade" 11.599
And I plug USB drive "to_upgrade" 2.959
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:49.376
Then the running Tails is installed on USB drive "to_upgrade" 24.187
And I unplug USB drive "to_upgrade" 0.244
And I unplug USB drive "__internal" 0.259
After features/support/hooks.rb:331 2.951
After features/support/hooks.rb:100 0.000
Tags: @product
1:32.260
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.179
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:22.481
Then all tps features from the old Tails version are active 1.443
And Tails is running from USB drive "to_upgrade" 0.381
And the boot device has safe access rights 3.370
And the expected persistent files created with the old Tails version are present in the filesystem 1.884
And all persistent directories from the old Tails version have safe access rights 2.518
After features/support/hooks.rb:331 0.684
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
4:47.219
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 13.231
And no SquashFS delta is installed 0.078
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.322
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.321
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.442
When the network is plugged 0.061
And Tor is ready 15.050
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.624
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.268
Given I shutdown Tails and wait for the computer to power off 11.788
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:29.626
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.837
And the file system changes introduced in version 6.2~testoverlayfs are present 0.441
And only the 6.2~testoverlayfs SquashFS delta is installed 0.061
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.161
# 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.257
When the network is plugged 0.053
And Tor is ready 13.973
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.688
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.282
Given I shutdown Tails and wait for the computer to power off 7.744
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:19.610
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.303
And the file system changes introduced in version 6.3~testoverlayfs are present 0.490
And only the 6.3~testoverlayfs SquashFS delta is installed 0.094
# 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.195
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.262
When the network is plugged 0.054
And Tor is ready 12.636
Then the Upgrader considers the system as up-to-date 0.110
# 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 18.163
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.877
After features/support/hooks.rb:331 1.180
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
42.804
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 22.477
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.277
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the signing key used by the Upgrader is outdated 0.058
But a current signing key is available on our website 0.000
When the network is plugged 0.054
And Tor is ready 19.259
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.611
After features/support/hooks.rb:331 5.738
After features/support/hooks.rb:100 0.000