Project Number Date
test_Tails_ISO_devel 4039 28 Oct 2025, 14:31

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:56.653 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:52.276
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.208
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 34.104
When I start Tails from USB drive "old" with network unplugged 1:12.354
Then the boot device has safe access rights 3.508
And Tails is running from USB drive "old" 0.302
And there is no persistence partition on USB drive "old" 0.078
And process "udev-watchdog" is running 0.123
And udev-watchdog is monitoring the correct device 0.241
And I unplug USB drive "old" 0.263
After features/support/hooks.rb:331 3.619
After features/support/hooks.rb:100 0.010
Tags: @product
2:12.550
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.176
And I start Tails from USB drive "old" with network unplugged and I login 1:29.948
Then Tails is running from USB drive "old" 0.671
And I create a persistent partition 31.587
And I take note of which tps features are available 1.360
Then a Tails persistence partition exists on USB drive "old" 0.806
And I shutdown Tails and wait for the computer to power off 7.999
After features/support/hooks.rb:331 0.587
After features/support/hooks.rb:100 0.010
Tags: @product
2:12.818
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.303
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:37.824
Then Tails is running from USB drive "old" 1.158
And all tps features are active 2.038
When I write some files expected to persist 1.719
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.221
And all persistence configuration files have safe access rights 0.393
And all persistent directories from the old Tails version have safe access rights 2.208
And I take note of which tps features are available 0.450
And I shutdown Tails and wait for the computer to power off 7.590
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.907
After features/support/hooks.rb:331 0.179
After features/support/hooks.rb:100 0.009
Tags: @product
2:40.063
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 14.219
And I log in to a new session 17.846
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.361
And I plug USB drive "to_upgrade" 2.519
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.499
Then the running Tails is installed on USB drive "to_upgrade" 23.217
And I unplug USB drive "to_upgrade" 0.196
And I unplug USB drive "__internal" 0.202
After features/support/hooks.rb:331 4.113
After features/support/hooks.rb:100 0.000
Tags: @product
1:52.377
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.225
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:42.627
Then all tps features from the old Tails version are active 2.089
And Tails is running from USB drive "to_upgrade" 0.346
And the boot device has safe access rights 3.486
And the expected persistent files created with the old Tails version are present in the filesystem 1.376
And all persistent directories from the old Tails version have safe access rights 2.223
After features/support/hooks.rb:331 1.041
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
5:39.306
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 15.223
And no SquashFS delta is installed 0.114
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.260
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.262
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.397
When the network is plugged 0.071
And Tor is ready 15.363
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.738
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.901
Given I shutdown Tails and wait for the computer to power off 8.594
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:45.760
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.316
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.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.193
# 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.241
When the network is plugged 0.057
And Tor is ready 12.243
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.831
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.354
Given I shutdown Tails and wait for the computer to power off 9.847
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:41.519
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 3.161
And the file system changes introduced in version 6.3~testoverlayfs are present 0.463
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.164
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.244
When the network is plugged 0.055
And Tor is ready 40.673
Then the Upgrader considers the system as up-to-date 0.219
# 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.984
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.528
After features/support/hooks.rb:331 1.064
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
27.261
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 12.010
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.329
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.068
But a current signing key is available on our website 0.000
When the network is plugged 0.059
And Tor is ready 12.552
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.186
After features/support/hooks.rb:331 1.222
After features/support/hooks.rb:100 0.000