Project Number Date
test_Tails_ISO_devel 4042 29 Oct 2025, 22:07

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 17:6.154 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:43.303
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.223
And I create a 7200 MiB disk named "old" 0.060
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 27.348
When I start Tails from USB drive "old" with network unplugged 1:10.845
Then the boot device has safe access rights 2.796
And Tails is running from USB drive "old" 0.384
And there is no persistence partition on USB drive "old" 0.057
And process "udev-watchdog" is running 0.062
And udev-watchdog is monitoring the correct device 0.292
And I unplug USB drive "old" 0.182
After features/support/hooks.rb:331 4.192
After features/support/hooks.rb:100 0.015
Tags: @product
2:11.828
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.206
And I start Tails from USB drive "old" with network unplugged and I login 1:29.427
Then Tails is running from USB drive "old" 0.620
And I create a persistent partition 29.806
And I take note of which tps features are available 1.576
Then a Tails persistence partition exists on USB drive "old" 2.194
And I shutdown Tails and wait for the computer to power off 7.997
After features/support/hooks.rb:331 0.266
After features/support/hooks.rb:100 0.010
Tags: @product
2:18.074
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.207
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:41.256
Then Tails is running from USB drive "old" 0.386
And all tps features are active 2.250
When I write some files expected to persist 1.687
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.163
And all persistence configuration files have safe access rights 0.374
And all persistent directories from the old Tails version have safe access rights 3.058
And I take note of which tps features are available 0.631
And I shutdown Tails and wait for the computer to power off 8.569
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.487
After features/support/hooks.rb:331 0.399
After features/support/hooks.rb:100 0.010
Tags: @product
2:36.050
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 without a persistent partition and stopped at Tails Greeter's login screen 12.192
And I log in to a new session 19.889
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.457
And I plug USB drive "to_upgrade" 2.576
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.530
Then the running Tails is installed on USB drive "to_upgrade" 21.949
And I unplug USB drive "to_upgrade" 0.235
And I unplug USB drive "__internal" 0.219
After features/support/hooks.rb:331 4.018
After features/support/hooks.rb:100 0.000
Tags: @product
1:55.942
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.211
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:45.573
Then all tps features from the old Tails version are active 1.566
And Tails is running from USB drive "to_upgrade" 0.303
And the boot device has safe access rights 4.157
And the expected persistent files created with the old Tails version are present in the filesystem 1.640
And all persistent directories from the old Tails version have safe access rights 2.489
After features/support/hooks.rb:331 1.003
After features/support/hooks.rb:100 0.041
Tags: @product @automatic_upgrade
5:53.016
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.317
And no SquashFS delta is installed 0.129
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.306
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.074
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.321
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.604
When the network is plugged 0.058
And Tor is ready 43.800
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.614
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.041
Given I shutdown Tails and wait for the computer to power off 10.442
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:45.277
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 2.639
And the file system changes introduced in version 6.2~testoverlayfs are present 0.279
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.166
# 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.282
When the network is plugged 0.065
And Tor is ready 11.837
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.207
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.091
Given I shutdown Tails and wait for the computer to power off 8.326
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:43.794
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.781
And the file system changes introduced in version 6.3~testoverlayfs are present 0.490
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.208
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.231
When the network is plugged 0.069
And Tor is ready 13.012
Then the Upgrader considers the system as up-to-date 10.842
# 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 6.998
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.553
After features/support/hooks.rb:331 1.269
After features/support/hooks.rb:100 0.031
Tags: @product @automatic_upgrade
27.937
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.192
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.306
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the signing key used by the Upgrader is outdated 0.073
But a current signing key is available on our website 0.000
When the network is plugged 0.066
And Tor is ready 10.925
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.308
After features/support/hooks.rb:331 1.169
After features/support/hooks.rb:100 0.000