Project Number Date
test_Tails_ISO_devel 4111 10 Dec 2025, 03:29

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 16:25.633 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:51.316
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.174
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.043
And I write an old version of the Tails USB image to disk "old" 28.005
When I start Tails from USB drive "old" with network unplugged 1:17.268
Then the boot device has safe access rights 3.859
And Tails is running from USB drive "old" 0.295
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.060
And udev-watchdog is monitoring the correct device 0.303
And I unplug USB drive "old" 0.192
After features/support/hooks.rb:331 4.015
After features/support/hooks.rb:100 0.015
Tags: @product
2:39.706
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 5.072
And I start Tails from USB drive "old" with network unplugged and I login 1:33.161
Then Tails is running from USB drive "old" 0.715
And I create a persistent partition 38.418
And I take note of which tps features are available 9.512
Then a Tails persistence partition exists on USB drive "old" 0.759
And I shutdown Tails and wait for the computer to power off 12.065
After features/support/hooks.rb:331 0.538
After features/support/hooks.rb:100 0.010
Tags: @product
2:51.597
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 1.386
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:6.227
Then Tails is running from USB drive "old" 0.307
And all tps features are active 6.930
When I write some files expected to persist 1.736
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.206
And all persistence configuration files have safe access rights 0.428
And all persistent directories from the old Tails version have safe access rights 2.577
And I take note of which tps features are available 0.811
And I shutdown Tails and wait for the computer to power off 11.300
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.683
After features/support/hooks.rb:331 0.535
After features/support/hooks.rb:100 0.008
Tags: @product
2:24.392
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 without a persistent partition and stopped at Tails Greeter's login screen 10.803
And I log in to a new session 11.384
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.338
And I plug USB drive "to_upgrade" 3.026
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.145
Then the running Tails is installed on USB drive "to_upgrade" 19.278
And I unplug USB drive "to_upgrade" 0.190
And I unplug USB drive "__internal" 0.225
After features/support/hooks.rb:331 3.682
After features/support/hooks.rb:100 0.000
Tags: @product
1:36.614
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.210
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:26.984
Then all tps features from the old Tails version are active 1.601
And Tails is running from USB drive "to_upgrade" 0.317
And the boot device has safe access rights 3.687
And the expected persistent files created with the old Tails version are present in the filesystem 1.394
And all persistent directories from the old Tails version have safe access rights 2.418
After features/support/hooks.rb:331 0.963
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
4:30.386
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.516
And no SquashFS delta is installed 0.111
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.289
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.263
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.481
When the network is plugged 1.718
And Tor is ready 12.029
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.577
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.904
Given I shutdown Tails and wait for the computer to power off 7.839
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:19.465
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.680
And the file system changes introduced in version 6.2~testoverlayfs are present 0.414
And only the 6.2~testoverlayfs SquashFS delta is installed 0.078
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.258
# 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.309
When the network is plugged 0.068
And Tor is ready 14.966
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.607
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.208
Given I shutdown Tails and wait for the computer to power off 7.800
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:24.160
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.170
And the file system changes introduced in version 6.3~testoverlayfs are present 0.502
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.257
When the network is plugged 0.054
And Tor is ready 21.932
Then the Upgrader considers the system as up-to-date 0.170
# 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 6.583
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.646
After features/support/hooks.rb:331 0.890
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
31.619
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 with a persistent partition enabled and logged in 10.318
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.302
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the signing key used by the Upgrader is outdated 0.081
But a current signing key is available on our website 0.000
When the network is plugged 0.079
And Tor is ready 18.874
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.894
After features/support/hooks.rb:331 0.802
After features/support/hooks.rb:100 0.000