Project Number Date
test_Tails_ISO_devel 4593 03 Sep 2026, 19:23

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 11:36.778 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:3.809
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.096
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.024
And I write an old version of the Tails USB image to disk "old" 14.640
When I start Tails from USB drive "old" with network unplugged 45.054
Then the boot device has safe access rights 2.397
And Tails is running from USB drive "old" 0.221
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.034
And udev-watchdog is monitoring the correct device 0.150
And I unplug USB drive "old" 0.126
After features/support/hooks.rb:339 3.715
After features/support/hooks.rb:108 0.006
Tags: @product
1:24.862
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.072
And I start Tails from USB drive "old" with network unplugged and I login 50.464
Then Tails is running from USB drive "old" 0.200
And I create a persistent partition 24.671
And I take note of which tps features are available 6.370
Then a Tails persistence partition exists on USB drive "old" 0.510
And I shutdown Tails and wait for the computer to power off 2.572
After features/support/hooks.rb:339 0.521
After features/support/hooks.rb:108 0.007
Tags: @product
1:36.893
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.104
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.601
Then Tails is running from USB drive "old" 0.261
And all tps features are active 8.429
When I write some files expected to persist 1.381
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.195
And all persistence configuration files have safe access rights 0.335
And all persistent directories from the old Tails version have safe access rights 1.995
And I take note of which tps features are available 7.042
And I shutdown Tails and wait for the computer to power off 4.255
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 12.291
After features/support/hooks.rb:339 0.457
After features/support/hooks.rb:108 0.007
Tags: @product
2:14.966
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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.693
And I log in to a new session 11.985
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.707
And I plug USB drive "to_upgrade" 2.195
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.749
Then the running Tails is installed on USB drive "to_upgrade" 19.385
And I unplug USB drive "to_upgrade" 0.130
And I unplug USB drive "__internal" 0.119
After features/support/hooks.rb:339 1.626
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.753
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.089
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.711
Then all tps features from the old Tails version are active 1.158
And Tails is running from USB drive "to_upgrade" 0.255
And the boot device has safe access rights 2.326
And the expected persistent files created with the old Tails version are present in the filesystem 0.872
And all persistent directories from the old Tails version have safe access rights 2.338
After features/support/hooks.rb:339 1.012
After features/support/hooks.rb:108 0.007
Tags: @product @automatic_upgrade
3:44.490
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.039
And no SquashFS delta is installed 0.084
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.236
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.216
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.331
When the network is plugged 0.030
And Tor is ready 13.287
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.603
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.602
Given I shutdown Tails and wait for the computer to power off 6.862
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.267
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.312
And the file system changes introduced in version 6.2~testoverlayfs are present 0.248
And only the 6.2~testoverlayfs SquashFS delta is installed 0.059
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.112
# 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.195
When the network is plugged 0.033
And Tor is ready 10.696
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.022
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.613
Given I shutdown Tails and wait for the computer to power off 4.293
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.792
Then Tails is running version 6.3~testoverlayfs 0.009
And all tps features are active 8.748
And the file system changes introduced in version 6.3~testoverlayfs are present 0.307
And only the 6.3~testoverlayfs SquashFS delta is installed 0.039
# 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.147
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.183
When the network is plugged 0.026
And Tor is ready 10.780
Then the Upgrader considers the system as up-to-date 0.124
# 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 3.733
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.405
After features/support/hooks.rb:339 0.918
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
20.001
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.232
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.231
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the signing key used by the Upgrader is outdated 0.047
But a current signing key is available on our website 0.000
When the network is plugged 0.031
And Tor is ready 9.699
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.711
After features/support/hooks.rb:339 0.712
After features/support/hooks.rb:108 0.000