Project Number Date
test_Tails_ISO_devel 4054 05 Nov 2025, 12: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 15:43.701 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:50.265
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.194
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 31.655
When I start Tails from USB drive "old" with network unplugged 1:13.820
Then the boot device has safe access rights 2.706
And Tails is running from USB drive "old" 0.275
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.236
And I unplug USB drive "old" 0.169
After features/support/hooks.rb:331 4.001
After features/support/hooks.rb:100 0.009
Tags: @product
2:0.923
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.160
And I start Tails from USB drive "old" with network unplugged and I login 1:22.118
Then Tails is running from USB drive "old" 0.362
And I create a persistent partition 28.972
And I take note of which tps features are available 1.085
Then a Tails persistence partition exists on USB drive "old" 0.634
And I shutdown Tails and wait for the computer to power off 7.589
After features/support/hooks.rb:331 0.504
After features/support/hooks.rb:100 0.009
Tags: @product
2:7.656
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.175
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:34.080
Then Tails is running from USB drive "old" 0.280
And all tps features are active 1.863
When I write some files expected to persist 1.513
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.244
And all persistence configuration files have safe access rights 0.395
And all persistent directories from the old Tails version have safe access rights 2.468
And I take note of which tps features are available 0.554
And I shutdown Tails and wait for the computer to power off 8.241
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.838
After features/support/hooks.rb:331 0.279
After features/support/hooks.rb:100 0.010
Tags: @product
2:32.667
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 11.988
And I log in to a new session 15.803
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.590
And I plug USB drive "to_upgrade" 2.633
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.776
Then the running Tails is installed on USB drive "to_upgrade" 20.478
And I unplug USB drive "to_upgrade" 0.191
And I unplug USB drive "__internal" 0.205
After features/support/hooks.rb:331 3.944
After features/support/hooks.rb:100 0.000
Tags: @product
1:47.759
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.195
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:38.918
Then all tps features from the old Tails version are active 1.529
And Tails is running from USB drive "to_upgrade" 0.297
And the boot device has safe access rights 3.084
And the expected persistent files created with the old Tails version are present in the filesystem 1.522
And all persistent directories from the old Tails version have safe access rights 2.212
After features/support/hooks.rb:331 0.619
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
4:59.493
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 14.878
And no SquashFS delta is installed 0.106
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.203
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.351
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.417
When the network is plugged 1.344
And Tor is ready 13.567
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.745
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.298
Given I shutdown Tails and wait for the computer to power off 11.114
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:38.675
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 2.223
And the file system changes introduced in version 6.2~testoverlayfs are present 0.336
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.176
# 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.242
When the network is plugged 0.057
And Tor is ready 11.692
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.710
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.358
Given I shutdown Tails and wait for the computer to power off 7.605
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:38.764
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 2.045
And the file system changes introduced in version 6.3~testoverlayfs are present 0.449
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.157
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.248
When the network is plugged 0.069
And Tor is ready 12.759
Then the Upgrader considers the system as up-to-date 0.195
# 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.076
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.423
After features/support/hooks.rb:331 1.131
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
24.935
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 11.029
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.313
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.091
And the signing key used by the Upgrader is outdated 0.070
But a current signing key is available on our website 0.000
When the network is plugged 0.087
And Tor is ready 10.390
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.952
After features/support/hooks.rb:331 0.932
After features/support/hooks.rb:100 0.000