Project Number Date
test_Tails_ISO_stable 6295 14 Apr 2026, 12:56

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:42.276 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:13.557
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.176
And I create a 7200 MiB disk named "old" 0.231
And I plug USB drive "old" 1.080
And I write an old version of the Tails USB image to disk "old" 15.238
When I start Tails from USB drive "old" with network unplugged 53.029
Then the boot device has safe access rights 2.930
And Tails is running from USB drive "old" 0.269
And there is no persistence partition on USB drive "old" 0.053
And process "udev-watchdog" is running 0.105
And udev-watchdog is monitoring the correct device 0.289
And I unplug USB drive "old" 0.151
After features/support/hooks.rb:331 3.616
After features/support/hooks.rb:100 0.008
Tags: @product
1:34.491
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.106
And I start Tails from USB drive "old" with network unplugged and I login 58.611
Then Tails is running from USB drive "old" 0.361
And I create a persistent partition 25.733
And I take note of which tps features are available 0.821
Then a Tails persistence partition exists on USB drive "old" 0.599
And I shutdown Tails and wait for the computer to power off 8.257
After features/support/hooks.rb:331 0.473
After features/support/hooks.rb:100 0.008
Tags: @product
1:31.719
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.091
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:7.136
Then Tails is running from USB drive "old" 0.305
And all tps features are active 1.394
When I write some files expected to persist 1.385
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.232
And all persistence configuration files have safe access rights 0.524
And all persistent directories from the old Tails version have safe access rights 2.297
And I take note of which tps features are available 0.204
And I shutdown Tails and wait for the computer to power off 4.040
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.107
After features/support/hooks.rb:331 0.242
After features/support/hooks.rb:100 0.010
Tags: @product
2:21.629
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 8.453
And I log in to a new session 17.129
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.892
And I plug USB drive "to_upgrade" 2.270
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.368
Then the running Tails is installed on USB drive "to_upgrade" 19.219
And I unplug USB drive "to_upgrade" 0.146
And I unplug USB drive "__internal" 0.149
After features/support/hooks.rb:331 2.662
After features/support/hooks.rb:100 0.000
Tags: @product
1:18.019
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.063
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:10.166
Then all tps features from the old Tails version are active 1.099
And Tails is running from USB drive "to_upgrade" 0.239
And the boot device has safe access rights 3.021
And the expected persistent files created with the old Tails version are present in the filesystem 1.253
And all persistent directories from the old Tails version have safe access rights 2.174
After features/support/hooks.rb:331 0.762
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
4:52.734
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.828
And no SquashFS delta is installed 0.219
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.640
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.113
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.311
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.530
When the network is plugged 0.032
And Tor is ready 22.606
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.567
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.284
Given I shutdown Tails and wait for the computer to power off 19.848
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:21.594
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.139
And the file system changes introduced in version 6.2~testoverlayfs are present 0.211
And only the 6.2~testoverlayfs SquashFS delta is installed 0.045
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.148
# 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.205
When the network is plugged 0.017
And Tor is ready 21.502
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.462
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.521
Given I shutdown Tails and wait for the computer to power off 12.407
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.976
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.090
And the file system changes introduced in version 6.3~testoverlayfs are present 0.412
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.163
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.288
When the network is plugged 0.053
And Tor is ready 22.742
Then the Upgrader considers the system as up-to-date 0.115
# 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.115
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.475
After features/support/hooks.rb:331 0.874
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
50.124
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.101
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.264
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.053
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 41.078
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.549
After features/support/hooks.rb:331 0.773
After features/support/hooks.rb:100 0.000