Project Number Date
test_Tails_ISO_stable 6204 15 Mar 2026, 11:13

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:41.978 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:12.361
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.059
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 15.078
When I start Tails from USB drive "old" with network unplugged 52.076
Then the boot device has safe access rights 3.177
And Tails is running from USB drive "old" 0.395
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.250
And I unplug USB drive "old" 0.143
After features/support/hooks.rb:331 1.630
After features/support/hooks.rb:100 0.008
Tags: @product
1:37.726
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.121
And I start Tails from USB drive "old" with network unplugged and I login 1:0.062
Then Tails is running from USB drive "old" 0.291
And I create a persistent partition 28.416
And I take note of which tps features are available 0.712
Then a Tails persistence partition exists on USB drive "old" 0.719
And I shutdown Tails and wait for the computer to power off 7.402
After features/support/hooks.rb:331 0.265
After features/support/hooks.rb:100 0.020
Tags: @product
1:36.977
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.092
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:8.210
Then Tails is running from USB drive "old" 0.273
And all tps features are active 1.219
When I write some files expected to persist 1.382
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.203
And all persistence configuration files have safe access rights 0.447
And all persistent directories from the old Tails version have safe access rights 2.730
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.234
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.952
After features/support/hooks.rb:331 0.404
After features/support/hooks.rb:100 0.008
Tags: @product
2:20.865
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 9.578
And I log in to a new session 13.489
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.332
And I plug USB drive "to_upgrade" 2.254
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.224
Then the running Tails is installed on USB drive "to_upgrade" 19.637
And I unplug USB drive "to_upgrade" 0.149
And I unplug USB drive "__internal" 0.199
After features/support/hooks.rb:331 2.370
After features/support/hooks.rb:100 0.000
Tags: @product
1:17.151
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.013
Given a computer 0.074
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.666
Then all tps features from the old Tails version are active 1.092
And Tails is running from USB drive "to_upgrade" 0.348
And the boot device has safe access rights 3.446
And the expected persistent files created with the old Tails version are present in the filesystem 1.408
And all persistent directories from the old Tails version have safe access rights 2.114
After features/support/hooks.rb:331 0.687
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:47.467
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.609
And no SquashFS delta is installed 0.077
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.254
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.234
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.423
When the network is plugged 0.019
And Tor is ready 21.817
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.426
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.732
Given I shutdown Tails and wait for the computer to power off 7.040
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:20.661
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.347
And the file system changes introduced in version 6.2~testoverlayfs are present 0.274
And only the 6.2~testoverlayfs SquashFS delta is installed 0.082
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.153
# 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.221
When the network is plugged 0.015
And Tor is ready 23.774
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.415
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.831
Given I shutdown Tails and wait for the computer to power off 18.104
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:19.806
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.559
And the file system changes introduced in version 6.3~testoverlayfs are present 0.373
And only the 6.3~testoverlayfs SquashFS delta is installed 0.052
# 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.171
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.197
When the network is plugged 0.024
And Tor is ready 23.209
Then the Upgrader considers the system as up-to-date 0.128
# 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.847
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.505
After features/support/hooks.rb:331 0.998
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
49.428
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 8.366
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.234
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.078
And the signing key used by the Upgrader is outdated 0.043
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 40.261
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.429
After features/support/hooks.rb:331 0.839
After features/support/hooks.rb:100 0.000