Project Number Date
test_Tails_ISO_stable 6277 08 Apr 2026, 14: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 12:49.194 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:16.682
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.062
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.423
When I start Tails from USB drive "old" with network unplugged 58.341
Then the boot device has safe access rights 3.122
And Tails is running from USB drive "old" 0.265
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.054
And udev-watchdog is monitoring the correct device 0.208
And I unplug USB drive "old" 0.135
After features/support/hooks.rb:331 1.388
After features/support/hooks.rb:100 0.007
Tags: @product
1:28.625
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 "old" with network unplugged and I login 55.368
Then Tails is running from USB drive "old" 0.293
And I create a persistent partition 23.732
And I take note of which tps features are available 0.703
Then a Tails persistence partition exists on USB drive "old" 0.531
And I shutdown Tails and wait for the computer to power off 7.932
After features/support/hooks.rb:331 0.238
After features/support/hooks.rb:100 0.007
Tags: @product
1:30.035
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.056
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.340
Then Tails is running from USB drive "old" 0.344
And all tps features are active 1.209
When I write some files expected to persist 1.358
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.234
And all persistence configuration files have safe access rights 0.520
And all persistent directories from the old Tails version have safe access rights 2.050
And I take note of which tps features are available 0.187
And I shutdown Tails and wait for the computer to power off 7.922
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.812
After features/support/hooks.rb:331 0.328
After features/support/hooks.rb:100 0.007
Tags: @product
2:11.993
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 without a persistent partition and stopped at Tails Greeter's login screen 7.833
And I log in to a new session 13.357
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.757
And I plug USB drive "to_upgrade" 2.248
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.364
Then the running Tails is installed on USB drive "to_upgrade" 16.137
And I unplug USB drive "to_upgrade" 0.155
And I unplug USB drive "__internal" 0.139
After features/support/hooks.rb:331 2.243
After features/support/hooks.rb:100 0.000
Tags: @product
1:10.494
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.080
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.718
Then all tps features from the old Tails version are active 1.152
And Tails is running from USB drive "to_upgrade" 0.235
And the boot device has safe access rights 2.421
And the expected persistent files created with the old Tails version are present in the filesystem 1.023
And all persistent directories from the old Tails version have safe access rights 1.863
After features/support/hooks.rb:331 0.818
After features/support/hooks.rb:100 0.027
4:44.027
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.254
And no SquashFS delta is installed 0.117
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.217
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.253
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.423
When the network is plugged 0.027
And Tor is ready 23.760
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.446
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.234
Given I shutdown Tails and wait for the computer to power off 20.295
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.459
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.106
And the file system changes introduced in version 6.2~testoverlayfs are present 0.161
And only the 6.2~testoverlayfs SquashFS delta is installed 0.044
# 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.212
When the network is plugged 0.017
And Tor is ready 21.455
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.361
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.195
Given I shutdown Tails and wait for the computer to power off 17.534
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.541
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.102
And the file system changes introduced in version 6.3~testoverlayfs are present 0.363
And only the 6.3~testoverlayfs SquashFS delta is installed 0.054
# 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.144
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.203
When the network is plugged 0.018
And Tor is ready 20.735
Then the Upgrader considers the system as up-to-date 0.116
# 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.356
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.606
After features/support/hooks.rb:331 0.989
After features/support/hooks.rb:100 0.012
27.335
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.025
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.244
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the signing key used by the Upgrader is outdated 0.066
But a current signing key is available on our website 0.000
When the network is plugged 0.055
And Tor is ready 18.485
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.413
After features/support/hooks.rb:331 0.904
After features/support/hooks.rb:100 0.000