Project Number Date
test_Tails_ISO_devel 4106 07 Dec 2025, 16:28

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 15:39.358 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:56.248
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.224
And I create a 7200 MiB disk named "old" 0.053
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 29.871
When I start Tails from USB drive "old" with network unplugged 1:20.037
Then the boot device has safe access rights 3.991
And Tails is running from USB drive "old" 0.333
And there is no persistence partition on USB drive "old" 0.077
And process "udev-watchdog" is running 0.051
And udev-watchdog is monitoring the correct device 0.301
And I unplug USB drive "old" 0.257
After features/support/hooks.rb:331 3.989
After features/support/hooks.rb:100 0.011
Tags: @product
2:15.935
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.213
And I start Tails from USB drive "old" with network unplugged and I login 1:28.042
Then Tails is running from USB drive "old" 0.379
And I create a persistent partition 35.740
And I take note of which tps features are available 1.449
Then a Tails persistence partition exists on USB drive "old" 0.729
And I shutdown Tails and wait for the computer to power off 9.381
After features/support/hooks.rb:331 0.939
After features/support/hooks.rb:100 0.014
Tags: @product
2:26.707
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given a computer 0.401
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:46.614
Then Tails is running from USB drive "old" 0.803
And all tps features are active 2.189
When I write some files expected to persist 1.934
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.237
And all persistence configuration files have safe access rights 0.554
And all persistent directories from the old Tails version have safe access rights 3.653
And I take note of which tps features are available 2.048
And I shutdown Tails and wait for the computer to power off 9.094
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.176
After features/support/hooks.rb:331 0.341
After features/support/hooks.rb:100 0.012
Tags: @product
2:35.346
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.682
And I log in to a new session 12.204
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.437
And I plug USB drive "to_upgrade" 3.625
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.615
Then the running Tails is installed on USB drive "to_upgrade" 23.305
And I unplug USB drive "to_upgrade" 0.180
And I unplug USB drive "__internal" 0.294
After features/support/hooks.rb:331 3.582
After features/support/hooks.rb:100 0.000
Tags: @product
1:34.424
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.194
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:21.267
Then all tps features from the old Tails version are active 1.962
And Tails is running from USB drive "to_upgrade" 0.333
And the boot device has safe access rights 4.376
And the expected persistent files created with the old Tails version are present in the filesystem 2.602
And all persistent directories from the old Tails version have safe access rights 3.689
After features/support/hooks.rb:331 1.214
After features/support/hooks.rb:100 0.012
4:26.898
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 10.767
And no SquashFS delta is installed 0.075
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.264
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.369
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.465
When the network is plugged 0.115
And Tor is ready 13.340
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.644
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.981
Given I shutdown Tails and wait for the computer to power off 4.874
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:21.016
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.560
And the file system changes introduced in version 6.2~testoverlayfs are present 0.294
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.191
# 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.248
When the network is plugged 0.071
And Tor is ready 14.165
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.877
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.802
Given I shutdown Tails and wait for the computer to power off 3.286
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:22.804
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 3.214
And the file system changes introduced in version 6.3~testoverlayfs are present 0.520
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.228
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.321
When the network is plugged 0.062
And Tor is ready 12.011
Then the Upgrader considers the system as up-to-date 10.677
# 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 5.853
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.551
After features/support/hooks.rb:331 0.926
After features/support/hooks.rb:100 0.020
23.795
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.942
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.253
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.063
But a current signing key is available on our website 0.000
When the network is plugged 0.060
And Tor is ready 11.332
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.084
After features/support/hooks.rb:331 1.117
After features/support/hooks.rb:100 0.000