Project Number Date
test_Tails_ISO_stable 6032 02 Jan 2026, 13:18

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 11:22.212 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.478
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.055
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.268
When I start Tails from USB drive "old" with network unplugged 54.729
Then the boot device has safe access rights 2.619
And Tails is running from USB drive "old" 0.278
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.275
And I unplug USB drive "old" 0.131
After features/support/hooks.rb:331 3.627
After features/support/hooks.rb:100 0.032
Tags: @product
1:24.907
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.076
And I start Tails from USB drive "old" with network unplugged and I login 51.471
Then Tails is running from USB drive "old" 0.246
And I create a persistent partition 23.862
And I take note of which tps features are available 0.651
Then a Tails persistence partition exists on USB drive "old" 0.481
And I shutdown Tails and wait for the computer to power off 8.118
After features/support/hooks.rb:331 0.413
After features/support/hooks.rb:100 0.006
Tags: @product
1:21.310
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.053
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.055
Then Tails is running from USB drive "old" 0.214
And all tps features are active 0.983
When I write some files expected to persist 1.180
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.171
And all persistence configuration files have safe access rights 0.274
And all persistent directories from the old Tails version have safe access rights 1.679
And I take note of which tps features are available 0.185
And I shutdown Tails and wait for the computer to power off 8.019
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.492
After features/support/hooks.rb:331 0.528
After features/support/hooks.rb:100 0.006
Tags: @product
2:9.609
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 without a persistent partition and stopped at Tails Greeter's login screen 8.380
And I log in to a new session 12.751
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.729
And I plug USB drive "to_upgrade" 2.246
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.226
Then the running Tails is installed on USB drive "to_upgrade" 13.993
And I unplug USB drive "to_upgrade" 0.136
And I unplug USB drive "__internal" 0.143
After features/support/hooks.rb:331 3.549
After features/support/hooks.rb:100 0.000
Tags: @product
1:5.366
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.060
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.032
Then all tps features from the old Tails version are active 0.959
And Tails is running from USB drive "to_upgrade" 0.195
And the boot device has safe access rights 2.479
And the expected persistent files created with the old Tails version are present in the filesystem 0.910
And all persistent directories from the old Tails version have safe access rights 1.729
After features/support/hooks.rb:331 0.884
After features/support/hooks.rb:100 0.005
Tags: @product @automatic_upgrade
3:50.208
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 8.147
And no SquashFS delta is installed 0.074
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.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.205
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.422
When the network is plugged 0.021
And Tor is ready 12.833
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.050
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.598
Given I shutdown Tails and wait for the computer to power off 9.388
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.005
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.062
And the file system changes introduced in version 6.2~testoverlayfs are present 0.238
And only the 6.2~testoverlayfs SquashFS delta is installed 0.034
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.135
# 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.234
When the network is plugged 0.013
And Tor is ready 9.837
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.049
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.122
Given I shutdown Tails and wait for the computer to power off 7.835
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.717
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.121
And the file system changes introduced in version 6.3~testoverlayfs are present 0.313
And only the 6.3~testoverlayfs SquashFS delta is installed 0.050
# 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.156
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.225
When the network is plugged 0.015
And Tor is ready 41.739
Then the Upgrader considers the system as up-to-date 0.093
# 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.758
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.426
After features/support/hooks.rb:331 0.726
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
18.330
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.268
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.190
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the signing key used by the Upgrader is outdated 0.040
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 9.733
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.039
After features/support/hooks.rb:331 0.903
After features/support/hooks.rb:100 0.000