Project Number Date
test_Tails_ISO_stable 6023 26 Dec 2025, 12:01

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 15:8.472 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
2:7.725
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.138
Given a computer 0.661
And I create a 7200 MiB disk named "old" 0.086
And I plug USB drive "old" 1.060
And I write an old version of the Tails USB image to disk "old" 45.004
When I start Tails from USB drive "old" with network unplugged 1:17.046
Then the boot device has safe access rights 3.030
And Tails is running from USB drive "old" 0.297
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.232
And I unplug USB drive "old" 0.189
After features/support/hooks.rb:331 3.718
After features/support/hooks.rb:100 0.009
Tags: @product
1:53.915
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.169
And I start Tails from USB drive "old" with network unplugged and I login 1:14.968
Then Tails is running from USB drive "old" 0.302
And I create a persistent partition 28.713
And I take note of which tps features are available 1.271
Then a Tails persistence partition exists on USB drive "old" 0.678
And I shutdown Tails and wait for the computer to power off 7.811
After features/support/hooks.rb:331 0.597
After features/support/hooks.rb:100 0.009
Tags: @product
1:51.411
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.163
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:18.585
Then Tails is running from USB drive "old" 0.297
And all tps features are active 1.912
When I write some files expected to persist 1.456
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.206
And all persistence configuration files have safe access rights 0.342
And all persistent directories from the old Tails version have safe access rights 2.179
And I take note of which tps features are available 0.444
And I shutdown Tails and wait for the computer to power off 7.662
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.159
After features/support/hooks.rb:331 0.549
After features/support/hooks.rb:100 0.015
Tags: @product
2:46.380
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.432
And I log in to a new session 17.463
And I clone USB drive "old" to a new USB drive "to_upgrade" 11.512
And I plug USB drive "to_upgrade" 2.805
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.065
Then the running Tails is installed on USB drive "to_upgrade" 21.632
And I unplug USB drive "to_upgrade" 0.214
And I unplug USB drive "__internal" 0.254
After features/support/hooks.rb:331 4.112
After features/support/hooks.rb:100 0.000
Tags: @product
1:23.189
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.161
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:14.909
Then all tps features from the old Tails version are active 1.790
And Tails is running from USB drive "to_upgrade" 0.285
And the boot device has safe access rights 2.711
And the expected persistent files created with the old Tails version are present in the filesystem 1.204
And all persistent directories from the old Tails version have safe access rights 2.126
After features/support/hooks.rb:331 0.758
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
4:13.083
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.832
And no SquashFS delta is installed 0.147
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.245
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.283
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.416
When the network is plugged 0.066
And Tor is ready 14.126
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.726
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.058
Given I shutdown Tails and wait for the computer to power off 11.146
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.524
Then Tails is running version 6.2~testoverlayfs 0.053
And all tps features are active 1.999
And the file system changes introduced in version 6.2~testoverlayfs are present 0.343
And only the 6.2~testoverlayfs SquashFS delta is installed 0.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.174
# 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.246
When the network is plugged 0.063
And Tor is ready 11.731
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.711
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.736
Given I shutdown Tails and wait for the computer to power off 7.728
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.896
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 1.979
And the file system changes introduced in version 6.3~testoverlayfs are present 0.411
And only the 6.3~testoverlayfs SquashFS delta is installed 0.058
# 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.157
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.228
When the network is plugged 0.054
And Tor is ready 12.412
Then the Upgrader considers the system as up-to-date 0.111
# 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.752
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.540
After features/support/hooks.rb:331 0.971
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
52.765
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.733
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.319
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.085
And the signing key used by the Upgrader is outdated 0.061
But a current signing key is available on our website 0.000
When the network is plugged 0.055
And Tor is ready 40.943
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.565
After features/support/hooks.rb:331 1.112
After features/support/hooks.rb:100 0.000