Project Number Date
test_Tails_ISO_devel 4287 21 Mar 2026, 11:11

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:47.573 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.689
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.060
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.027
And I write an old version of the Tails USB image to disk "old" 13.730
When I start Tails from USB drive "old" with network unplugged 42.197
Then the boot device has safe access rights 2.974
And Tails is running from USB drive "old" 0.256
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.053
And udev-watchdog is monitoring the correct device 0.205
And I unplug USB drive "old" 0.130
After features/support/hooks.rb:331 1.339
After features/support/hooks.rb:100 0.006
Tags: @product
1:30.018
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.058
And I start Tails from USB drive "old" with network unplugged and I login 54.700
Then Tails is running from USB drive "old" 0.307
And I create a persistent partition 25.064
And I take note of which tps features are available 0.834
Then a Tails persistence partition exists on USB drive "old" 0.592
And I shutdown Tails and wait for the computer to power off 8.460
After features/support/hooks.rb:331 0.381
After features/support/hooks.rb:100 0.007
Tags: @product
1:30.636
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.061
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.149
Then Tails is running from USB drive "old" 0.296
And all tps features are active 1.359
When I write some files expected to persist 1.296
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.161
And all persistence configuration files have safe access rights 0.444
And all persistent directories from the old Tails version have safe access rights 1.970
And I take note of which tps features are available 0.179
And I shutdown Tails and wait for the computer to power off 8.262
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.454
After features/support/hooks.rb:331 0.275
After features/support/hooks.rb:100 0.007
Tags: @product
2:10.378
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.789
And I log in to a new session 12.540
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.803
And I plug USB drive "to_upgrade" 2.251
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.986
Then the running Tails is installed on USB drive "to_upgrade" 14.734
And I unplug USB drive "to_upgrade" 0.141
And I unplug USB drive "__internal" 0.130
After features/support/hooks.rb:331 2.422
After features/support/hooks.rb:100 0.000
Tags: @product
1:11.547
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.051
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.799
Then all tps features from the old Tails version are active 0.940
And Tails is running from USB drive "to_upgrade" 0.256
And the boot device has safe access rights 2.615
And the expected persistent files created with the old Tails version are present in the filesystem 1.081
And all persistent directories from the old Tails version have safe access rights 1.803
After features/support/hooks.rb:331 0.672
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:37.283
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.518
And no SquashFS delta is installed 0.072
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.223
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.309
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.437
When the network is plugged 0.016
And Tor is ready 21.836
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.472
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.434
Given I shutdown Tails and wait for the computer to power off 20.202
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.165
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 1.233
And the file system changes introduced in version 6.2~testoverlayfs are present 0.228
And only the 6.2~testoverlayfs SquashFS delta is installed 0.052
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.139
# 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.269
When the network is plugged 0.015
And Tor is ready 20.612
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.394
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.201
Given I shutdown Tails and wait for the computer to power off 17.506
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.496
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 1.236
And the file system changes introduced in version 6.3~testoverlayfs are present 0.414
And only the 6.3~testoverlayfs SquashFS delta is installed 0.046
# 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.153
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.205
When the network is plugged 0.057
And Tor is ready 20.464
Then the Upgrader considers the system as up-to-date 0.150
# 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.274
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.356
After features/support/hooks.rb:331 0.645
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
47.019
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.373
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.301
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 0.047
But a current signing key is available on our website 0.000
When the network is plugged 0.030
And Tor is ready 38.857
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.358
After features/support/hooks.rb:331 0.815
After features/support/hooks.rb:100 0.000