Project Number Date
test_Tails_ISO_devel 4277 13 Mar 2026, 07:36

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:52.925 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:12.766
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.077
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 14.286
When I start Tails from USB drive "old" with network unplugged 53.761
Then the boot device has safe access rights 2.873
And Tails is running from USB drive "old" 0.323
And there is no persistence partition on USB drive "old" 0.052
And process "udev-watchdog" is running 0.039
And udev-watchdog is monitoring the correct device 0.191
And I unplug USB drive "old" 0.135
After features/support/hooks.rb:331 1.358
After features/support/hooks.rb:100 0.006
Tags: @product
1:29.449
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.050
And I start Tails from USB drive "old" with network unplugged and I login 54.038
Then Tails is running from USB drive "old" 0.310
And I create a persistent partition 25.324
And I take note of which tps features are available 0.866
Then a Tails persistence partition exists on USB drive "old" 0.572
And I shutdown Tails and wait for the computer to power off 8.286
After features/support/hooks.rb:331 0.499
After features/support/hooks.rb:100 0.008
Tags: @product
1:28.246
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.063
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.192
Then Tails is running from USB drive "old" 0.235
And all tps features are active 1.097
When I write some files expected to persist 1.490
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.177
And all persistence configuration files have safe access rights 0.433
And all persistent directories from the old Tails version have safe access rights 1.994
And I take note of which tps features are available 0.180
And I shutdown Tails and wait for the computer to power off 8.281
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.099
After features/support/hooks.rb:331 0.621
After features/support/hooks.rb:100 0.006
Tags: @product
2:13.186
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.469
And I log in to a new session 11.748
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.013
And I plug USB drive "to_upgrade" 2.289
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.311
Then the running Tails is installed on USB drive "to_upgrade" 16.073
And I unplug USB drive "to_upgrade" 0.140
And I unplug USB drive "__internal" 0.139
After features/support/hooks.rb:331 1.966
After features/support/hooks.rb:100 0.000
Tags: @product
1:11.625
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.049
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.159
Then all tps features from the old Tails version are active 1.049
And Tails is running from USB drive "to_upgrade" 0.321
And the boot device has safe access rights 2.766
And the expected persistent files created with the old Tails version are present in the filesystem 1.283
And all persistent directories from the old Tails version have safe access rights 1.995
After features/support/hooks.rb:331 0.629
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
4:51.840
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.409
And no SquashFS delta is installed 0.146
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.186
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.247
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.464
When the network is plugged 0.019
And Tor is ready 20.266
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.423
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.287
Given I shutdown Tails and wait for the computer to power off 15.001
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.184
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.085
And the file system changes introduced in version 6.2~testoverlayfs are present 0.243
And only the 6.2~testoverlayfs SquashFS delta is installed 0.038
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.122
# 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.215
When the network is plugged 0.017
And Tor is ready 41.236
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.454
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.442
Given I shutdown Tails and wait for the computer to power off 17.675
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.462
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 1.163
And the file system changes introduced in version 6.3~testoverlayfs are present 0.338
And only the 6.3~testoverlayfs SquashFS delta is installed 0.064
# 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.128
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.199
When the network is plugged 0.013
And Tor is ready 20.877
Then the Upgrader considers the system as up-to-date 0.099
# 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.817
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.449
After features/support/hooks.rb:331 0.734
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
25.811
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 7.565
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.215
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the signing key used by the Upgrader is outdated 0.041
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 17.531
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.397
After features/support/hooks.rb:331 0.945
After features/support/hooks.rb:100 0.000