Project Number Date
test_Tails_ISO_stable 6359 08 May 2026, 11:20

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:22.705 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:0.630
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.084
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.555
When I start Tails from USB drive "old" with network unplugged 42.112
Then the boot device has safe access rights 3.061
And Tails is running from USB drive "old" 0.276
And there is no persistence partition on USB drive "old" 0.080
And process "udev-watchdog" is running 0.056
And udev-watchdog is monitoring the correct device 0.235
And I unplug USB drive "old" 0.142
After features/support/hooks.rb:331 1.391
After features/support/hooks.rb:100 0.007
Tags: @product
1:26.015
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login 53.071
Then Tails is running from USB drive "old" 0.265
And I create a persistent partition 24.723
And I take note of which tps features are available 0.669
Then a Tails persistence partition exists on USB drive "old" 0.536
And I shutdown Tails and wait for the computer to power off 6.695
After features/support/hooks.rb:331 0.299
After features/support/hooks.rb:100 0.007
Tags: @product
1:29.471
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.053
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.890
Then Tails is running from USB drive "old" 0.255
And all tps features are active 1.122
When I write some files expected to persist 1.376
# 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.398
And all persistent directories from the old Tails version have safe access rights 1.816
And I take note of which tps features are available 0.231
And I shutdown Tails and wait for the computer to power off 8.523
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.636
After features/support/hooks.rb:331 0.409
After features/support/hooks.rb:100 0.010
Tags: @product
2:12.150
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.135
And I log in to a new session 12.526
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.934
And I plug USB drive "to_upgrade" 2.251
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.858
Then the running Tails is installed on USB drive "to_upgrade" 16.156
And I unplug USB drive "to_upgrade" 0.143
And I unplug USB drive "__internal" 0.144
After features/support/hooks.rb:331 3.550
After features/support/hooks.rb:100 0.000
Tags: @product
1:11.378
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.061
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.551
Then all tps features from the old Tails version are active 1.215
And Tails is running from USB drive "to_upgrade" 0.279
And the boot device has safe access rights 2.939
And the expected persistent files created with the old Tails version are present in the filesystem 1.277
And all persistent directories from the old Tails version have safe access rights 2.051
After features/support/hooks.rb:331 0.855
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:37.244
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 8.287
And no SquashFS delta is installed 0.062
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.221
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.247
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.348
When the network is plugged 0.018
And Tor is ready 21.779
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.477
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.497
Given I shutdown Tails and wait for the computer to power off 18.968
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.406
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.424
And the file system changes introduced in version 6.2~testoverlayfs are present 0.287
And only the 6.2~testoverlayfs SquashFS delta is installed 0.055
# 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.252
When the network is plugged 0.023
And Tor is ready 20.254
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.376
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.310
Given I shutdown Tails and wait for the computer to power off 17.390
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.435
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.199
And the file system changes introduced in version 6.3~testoverlayfs are present 0.525
And only the 6.3~testoverlayfs SquashFS delta is installed 0.061
# 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.165
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.224
When the network is plugged 0.015
And Tor is ready 20.487
Then the Upgrader considers the system as up-to-date 0.113
# 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.746
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.377
After features/support/hooks.rb:331 0.788
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
25.815
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.310
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.239
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the signing key used by the Upgrader is outdated 0.063
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 17.733
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.403
After features/support/hooks.rb:331 0.938
After features/support/hooks.rb:100 0.000