Project Number Date
test_Tails_ISO_devel 4293 25 Mar 2026, 14:09

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 13:26.490 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:23.761
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.064
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 14.493
When I start Tails from USB drive "old" with network unplugged 1:4.389
Then the boot device has safe access rights 2.885
And Tails is running from USB drive "old" 0.370
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.062
And udev-watchdog is monitoring the correct device 0.248
And I unplug USB drive "old" 0.157
After features/support/hooks.rb:331 1.525
After features/support/hooks.rb:100 0.007
Tags: @product
1:33.047
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.059
And I start Tails from USB drive "old" with network unplugged and I login 57.543
Then Tails is running from USB drive "old" 0.361
And I create a persistent partition 25.252
And I take note of which tps features are available 0.843
Then a Tails persistence partition exists on USB drive "old" 0.667
And I shutdown Tails and wait for the computer to power off 8.319
After features/support/hooks.rb:331 0.341
After features/support/hooks.rb:100 0.007
Tags: @product
1:33.639
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.062
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:9.386
Then Tails is running from USB drive "old" 0.256
And all tps features are active 1.474
When I write some files expected to persist 1.746
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.204
And all persistence configuration files have safe access rights 0.530
And all persistent directories from the old Tails version have safe access rights 2.139
And I take note of which tps features are available 0.188
And I shutdown Tails and wait for the computer to power off 4.315
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.332
After features/support/hooks.rb:331 0.276
After features/support/hooks.rb:100 0.006
Tags: @product
2:18.779
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 9.421
And I log in to a new session 15.618
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.885
And I plug USB drive "to_upgrade" 2.273
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.737
Then the running Tails is installed on USB drive "to_upgrade" 17.517
And I unplug USB drive "to_upgrade" 0.157
And I unplug USB drive "__internal" 0.167
After features/support/hooks.rb:331 2.685
After features/support/hooks.rb:100 0.000
Tags: @product
1:14.341
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.049
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.417
Then all tps features from the old Tails version are active 1.063
And Tails is running from USB drive "to_upgrade" 0.367
And the boot device has safe access rights 2.775
And the expected persistent files created with the old Tails version are present in the filesystem 1.149
And all persistent directories from the old Tails version have safe access rights 2.519
After features/support/hooks.rb:331 0.934
After features/support/hooks.rb:100 0.006
4:55.231
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 8.779
And no SquashFS delta is installed 0.083
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.210
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.246
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.390
When the network is plugged 0.017
And Tor is ready 24.480
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.562
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.121
Given I shutdown Tails and wait for the computer to power off 20.905
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.803
Then Tails is running version 6.2~testoverlayfs 0.009
And all tps features are active 1.238
And the file system changes introduced in version 6.2~testoverlayfs are present 0.251
And only the 6.2~testoverlayfs SquashFS delta is installed 0.052
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.158
# 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.019
And Tor is ready 22.873
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.438
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.097
Given I shutdown Tails and wait for the computer to power off 18.192
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:19.508
Then Tails is running version 6.3~testoverlayfs 0.009
And all tps features are active 1.358
And the file system changes introduced in version 6.3~testoverlayfs are present 0.400
And only the 6.3~testoverlayfs SquashFS delta is installed 0.049
# 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.173
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.215
When the network is plugged 0.019
And Tor is ready 21.314
Then the Upgrader considers the system as up-to-date 0.096
# 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.505
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.379
After features/support/hooks.rb:331 0.898
After features/support/hooks.rb:100 0.012
27.689
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.452
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.273
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.044
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 18.481
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.376
After features/support/hooks.rb:331 0.643
After features/support/hooks.rb:100 0.000