Project Number Date
test_Tails_ISO_devel 4260 01 Mar 2026, 11:37

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:58.742 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:9.620
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.054
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 14.360
When I start Tails from USB drive "old" with network unplugged 50.498
Then the boot device has safe access rights 2.938
And Tails is running from USB drive "old" 0.292
And there is no persistence partition on USB drive "old" 0.048
And process "udev-watchdog" is running 0.053
And udev-watchdog is monitoring the correct device 0.197
And I unplug USB drive "old" 0.147
After features/support/hooks.rb:331 3.602
After features/support/hooks.rb:100 0.039
Tags: @product
1:24.206
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 53.516
Then Tails is running from USB drive "old" 0.429
And I create a persistent partition 24.612
And I take note of which tps features are available 0.784
Then a Tails persistence partition exists on USB drive "old" 0.575
And I shutdown Tails and wait for the computer to power off 4.229
After features/support/hooks.rb:331 0.173
After features/support/hooks.rb:100 0.014
Tags: @product
1:27.573
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.069
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.615
Then Tails is running from USB drive "old" 0.235
And all tps features are active 1.019
When I write some files expected to persist 1.195
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.166
And all persistence configuration files have safe access rights 0.431
And all persistent directories from the old Tails version have safe access rights 1.987
And I take note of which tps features are available 0.177
And I shutdown Tails and wait for the computer to power off 8.166
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.507
After features/support/hooks.rb:331 0.338
After features/support/hooks.rb:100 0.011
Tags: @product
2:17.721
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 8.245
And I log in to a new session 11.513
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.774
And I plug USB drive "to_upgrade" 2.305
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.399
Then the running Tails is installed on USB drive "to_upgrade" 16.192
And I unplug USB drive "to_upgrade" 0.139
And I unplug USB drive "__internal" 0.151
After features/support/hooks.rb:331 2.737
After features/support/hooks.rb:100 0.000
Tags: @product
1:15.437
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.046
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.610
Then all tps features from the old Tails version are active 1.078
And Tails is running from USB drive "to_upgrade" 0.236
And the boot device has safe access rights 2.519
And the expected persistent files created with the old Tails version are present in the filesystem 1.137
And all persistent directories from the old Tails version have safe access rights 1.807
After features/support/hooks.rb:331 0.830
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
4:57.512
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.618
And no SquashFS delta is installed 0.192
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.272
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.272
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.335
When the network is plugged 0.015
And Tor is ready 20.992
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.413
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.398
Given I shutdown Tails and wait for the computer to power off 20.805
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.506
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 1.207
And the file system changes introduced in version 6.2~testoverlayfs are present 0.201
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.140
# 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.014
And Tor is ready 41.279
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.381
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.295
Given I shutdown Tails and wait for the computer to power off 17.515
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.417
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.159
And the file system changes introduced in version 6.3~testoverlayfs are present 0.394
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.121
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.228
When the network is plugged 0.023
And Tor is ready 22.108
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.251
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.380
After features/support/hooks.rb:331 0.771
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
26.671
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 7.532
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.355
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the signing key used by the Upgrader is outdated 0.042
But a current signing key is available on our website 0.000
When the network is plugged 0.022
And Tor is ready 18.153
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.524
After features/support/hooks.rb:331 0.632
After features/support/hooks.rb:100 0.000