Project Number Date
test_Tails_ISO_devel 4092 28 Nov 2025, 20:57

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 19:26.870 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:17.225
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.173
And I create a 7200 MiB disk named "old" 0.062
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 40.528
When I start Tails from USB drive "old" with network unplugged 1:31.577
Then the boot device has safe access rights 2.965
And Tails is running from USB drive "old" 0.293
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.261
And I unplug USB drive "old" 0.180
After features/support/hooks.rb:331 3.653
After features/support/hooks.rb:100 0.008
Tags: @product
2:12.127
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.184
And I start Tails from USB drive "old" with network unplugged and I login 1:28.781
Then Tails is running from USB drive "old" 0.707
And I create a persistent partition 31.731
And I take note of which tps features are available 1.477
Then a Tails persistence partition exists on USB drive "old" 1.234
And I shutdown Tails and wait for the computer to power off 8.010
After features/support/hooks.rb:331 0.544
After features/support/hooks.rb:100 0.010
Tags: @product
2:13.582
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.367
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:42.430
Then Tails is running from USB drive "old" 0.292
And all tps features are active 1.850
When I write some files expected to persist 1.618
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.208
And all persistence configuration files have safe access rights 0.333
And all persistent directories from the old Tails version have safe access rights 2.332
And I take note of which tps features are available 0.575
And I shutdown Tails and wait for the computer to power off 3.954
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.617
After features/support/hooks.rb:331 0.482
After features/support/hooks.rb:100 0.009
Tags: @product
2:37.204
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 13.009
And I log in to a new session 17.125
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.791
And I plug USB drive "to_upgrade" 2.483
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.445
Then the running Tails is installed on USB drive "to_upgrade" 22.597
And I unplug USB drive "to_upgrade" 0.426
And I unplug USB drive "__internal" 0.325
After features/support/hooks.rb:331 3.866
After features/support/hooks.rb:100 0.000
Tags: @product
2:0.847
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.173
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:50.526
Then all tps features from the old Tails version are active 1.528
And Tails is running from USB drive "to_upgrade" 0.316
And the boot device has safe access rights 4.081
And the expected persistent files created with the old Tails version are present in the filesystem 1.529
And all persistent directories from the old Tails version have safe access rights 2.691
After features/support/hooks.rb:331 0.665
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
7:24.496
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 13.433
And no SquashFS delta is installed 0.527
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.308
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.083
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.338
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.593
When the network is plugged 0.052
And Tor is ready 14.212
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.882
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.621
Given I shutdown Tails and wait for the computer to power off 11.387
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.830
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.659
And the file system changes introduced in version 6.2~testoverlayfs are present 0.365
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.210
# 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.229
When the network is plugged 0.049
And Tor is ready 13.157
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2:4.761
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.693
Given I shutdown Tails and wait for the computer to power off 5.866
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:41.043
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.733
And the file system changes introduced in version 6.3~testoverlayfs are present 0.500
And only the 6.3~testoverlayfs SquashFS delta is installed 0.091
# 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.183
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.286
When the network is plugged 0.066
And Tor is ready 17.080
Then the Upgrader considers the system as up-to-date 0.258
# 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.427
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.458
After features/support/hooks.rb:331 1.826
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
41.387
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 21.662
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.295
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the signing key used by the Upgrader is outdated 0.062
But a current signing key is available on our website 0.000
When the network is plugged 0.077
And Tor is ready 17.528
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.713
After features/support/hooks.rb:331 5.561
After features/support/hooks.rb:100 0.000