Project Number Date
test_Tails_ISO_stable 6694 26 Sep 2026, 21:21

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 12:59.365 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:3.177
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.091
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.108
When I start Tails from USB drive "old" with network unplugged 46.546
Then the boot device has safe access rights 1.789
And Tails is running from USB drive "old" 0.207
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.041
And udev-watchdog is monitoring the correct device 0.182
And I unplug USB drive "old" 0.128
After features/support/hooks.rb:339 3.449
After features/support/hooks.rb:108 0.005
Tags: @product
1:18.864
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.098
And I start Tails from USB drive "old" with network unplugged and I login 46.831
Then Tails is running from USB drive "old" 0.174
And I create a persistent partition 22.640
And I take note of which tps features are available 6.078
Then a Tails persistence partition exists on USB drive "old" 0.464
And I shutdown Tails and wait for the computer to power off 2.576
After features/support/hooks.rb:339 0.491
After features/support/hooks.rb:108 0.005
Tags: @product
1:26.949
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.082
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.700
Then Tails is running from USB drive "old" 0.217
And all tps features are active 6.508
When I write some files expected to persist 0.877
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.234
And all persistence configuration files have safe access rights 0.310
And all persistent directories from the old Tails version have safe access rights 1.551
And I take note of which tps features are available 5.626
And I shutdown Tails and wait for the computer to power off 2.603
# 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" 11.236
After features/support/hooks.rb:339 0.319
After features/support/hooks.rb:108 0.006
Tags: @product
2:10.085
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.642
And I log in to a new session 10.927
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.584
And I plug USB drive "to_upgrade" 2.215
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.744
Then the running Tails is installed on USB drive "to_upgrade" 16.729
And I unplug USB drive "to_upgrade" 0.118
And I unplug USB drive "__internal" 0.123
After features/support/hooks.rb:339 1.619
After features/support/hooks.rb:108 0.000
Tags: @product
1:3.666
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.079
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.446
Then all tps features from the old Tails version are active 0.965
And Tails is running from USB drive "to_upgrade" 0.154
And the boot device has safe access rights 1.747
And the expected persistent files created with the old Tails version are present in the filesystem 0.942
And all persistent directories from the old Tails version have safe access rights 1.328
After features/support/hooks.rb:339 0.471
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
5:39.256
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.087
And no SquashFS delta is installed 0.078
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.180
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.186
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.345
When the network is plugged 0.034
And Tor is ready 10.755
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2:2.479
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.176
Given I shutdown Tails and wait for the computer to power off 4.077
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.265
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.293
And the file system changes introduced in version 6.2~testoverlayfs are present 0.154
And only the 6.2~testoverlayfs SquashFS delta is installed 0.041
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.088
# 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.145
When the network is plugged 0.025
And Tor is ready 10.059
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 9.681
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.454
Given I shutdown Tails and wait for the computer to power off 3.870
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.795
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 7.301
And the file system changes introduced in version 6.3~testoverlayfs are present 0.263
And only the 6.3~testoverlayfs SquashFS delta is installed 0.051
# 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.122
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.150
When the network is plugged 0.036
And Tor is ready 10.305
Then the Upgrader considers the system as up-to-date 10.384
# 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.005
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.308
After features/support/hooks.rb:339 0.705
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
17.367
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.798
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.208
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.041
But a current signing key is available on our website 0.000
When the network is plugged 0.033
And Tor is ready 7.868
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.363
After features/support/hooks.rb:339 0.774
After features/support/hooks.rb:108 0.000