Project Number Date
test_Tails_ISO_stable 6219 20 Mar 2026, 11:07

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 13:4.202 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:23.304
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.065
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 14.401
When I start Tails from USB drive "old" with network unplugged 1:3.827
Then the boot device has safe access rights 3.206
And Tails is running from USB drive "old" 0.274
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.051
And udev-watchdog is monitoring the correct device 0.263
And I unplug USB drive "old" 0.145
After features/support/hooks.rb:331 4.204
After features/support/hooks.rb:100 0.009
Tags: @product
1:27.777
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.095
And I start Tails from USB drive "old" with network unplugged and I login 56.155
Then Tails is running from USB drive "old" 0.395
And I create a persistent partition 25.103
And I take note of which tps features are available 0.794
Then a Tails persistence partition exists on USB drive "old" 0.731
And I shutdown Tails and wait for the computer to power off 4.501
After features/support/hooks.rb:331 0.606
After features/support/hooks.rb:100 0.007
Tags: @product
1:30.086
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.055
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.442
Then Tails is running from USB drive "old" 0.396
And all tps features are active 1.228
When I write some files expected to persist 1.386
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.187
And all persistence configuration files have safe access rights 0.384
And all persistent directories from the old Tails version have safe access rights 2.345
And I take note of which tps features are available 0.231
And I shutdown Tails and wait for the computer to power off 7.247
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.179
After features/support/hooks.rb:331 0.281
After features/support/hooks.rb:100 0.009
Tags: @product
2:18.064
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 without a persistent partition and stopped at Tails Greeter's login screen 10.218
And I log in to a new session 14.645
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.077
And I plug USB drive "to_upgrade" 2.242
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.613
Then the running Tails is installed on USB drive "to_upgrade" 17.725
And I unplug USB drive "to_upgrade" 0.311
And I unplug USB drive "__internal" 0.228
After features/support/hooks.rb:331 3.067
After features/support/hooks.rb:100 0.000
Tags: @product
1:14.264
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.064
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.229
Then all tps features from the old Tails version are active 1.004
And Tails is running from USB drive "to_upgrade" 0.234
And the boot device has safe access rights 2.432
And the expected persistent files created with the old Tails version are present in the filesystem 1.185
And all persistent directories from the old Tails version have safe access rights 2.113
After features/support/hooks.rb:331 0.619
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
4:43.495
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.536
And no SquashFS delta is installed 0.071
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.216
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.256
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.374
When the network is plugged 0.022
And Tor is ready 21.075
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.411
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.740
Given I shutdown Tails and wait for the computer to power off 15.424
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.941
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 1.214
And the file system changes introduced in version 6.2~testoverlayfs are present 0.228
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.142
# 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.239
When the network is plugged 0.025
And Tor is ready 21.508
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.378
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.210
Given I shutdown Tails and wait for the computer to power off 17.750
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.262
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.057
And the file system changes introduced in version 6.3~testoverlayfs are present 0.382
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.132
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.220
When the network is plugged 0.017
And Tor is ready 22.536
Then the Upgrader considers the system as up-to-date 0.141
# 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 5.199
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.567
After features/support/hooks.rb:331 1.008
After features/support/hooks.rb:100 0.040
Tags: @product @automatic_upgrade
27.209
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 7.810
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.243
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.030
And the signing key used by the Upgrader is outdated 0.050
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 18.652
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.405
After features/support/hooks.rb:331 1.025
After features/support/hooks.rb:100 0.000