Project Number Date
test_Tails_ISO_20979-pdfarranger 15 10 Jun 2025, 02:43

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 19:55.255 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
2:29.751
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.178
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 31.691
When I start Tails from USB drive "old" with network unplugged 1:52.733
Then the boot device has safe access rights 3.001
And Tails is running from USB drive "old" 0.331
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.102
And udev-watchdog is monitoring the correct device 0.315
And I unplug USB drive "old" 0.233
After features/support/hooks.rb:330 3.539
After features/support/hooks.rb:100 0.008
Tags: @product
2:15.769
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.205
And I start Tails from USB drive "old" with network unplugged and I login 1:32.913
Then Tails is running from USB drive "old" 0.378
And I create a persistent partition 31.151
And I take note of which tps features are available 1.992
Then a Tails persistence partition exists on USB drive "old" 0.741
And I shutdown Tails and wait for the computer to power off 8.386
After features/support/hooks.rb:330 0.176
After features/support/hooks.rb:100 0.010
Tags: @product
2:53.079
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.216
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.145
Then Tails is running from USB drive "old" 0.420
And all tps features are active 2.059
When I write some files expected to persist 2.232
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.215
And all persistence configuration files have safe access rights 0.433
And all persistent directories from the old Tails version have safe access rights 2.672
And I take note of which tps features are available 0.456
And I shutdown Tails and wait for the computer to power off 4.389
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.837
After features/support/hooks.rb:330 0.116
After features/support/hooks.rb:100 0.008
Tags: @product
2:33.605
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 10.616
And I log in to a new session 19.105
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.365
And I plug USB drive "to_upgrade" 2.405
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.129
Then the running Tails is installed on USB drive "to_upgrade" 24.576
And I unplug USB drive "to_upgrade" 0.199
And I unplug USB drive "__internal" 0.207
After features/support/hooks.rb:330 1.928
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.278
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.221
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.620
Then all tps features from the old Tails version are active 1.731
And Tails is running from USB drive "to_upgrade" 0.333
And the boot device has safe access rights 3.419
And the expected persistent files created with the old Tails version are present in the filesystem 1.472
And all persistent directories from the old Tails version have safe access rights 2.479
After features/support/hooks.rb:330 1.239
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
6:46.854
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.655
And no SquashFS delta is installed 0.159
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.450
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.103
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.474
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.509
When the network is plugged 0.073
And Tor is ready 26.266
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.862
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.821
Given I shutdown Tails and wait for the computer to power off 10.919
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.354
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.233
And the file system changes introduced in version 6.2~testoverlayfs are present 0.343
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.311
# 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.259
When the network is plugged 0.084
And Tor is ready 18.573
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.854
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.527
Given I shutdown Tails and wait for the computer to power off 4.261
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.664
Then Tails is running version 6.3~testoverlayfs 0.028
And all tps features are active 2.027
And the file system changes introduced in version 6.3~testoverlayfs are present 0.434
And only the 6.3~testoverlayfs SquashFS delta is installed 0.101
# 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.316
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.268
When the network is plugged 0.105
And Tor is ready 19.091
Then the Upgrader considers the system as up-to-date 0.316
# 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 16.489
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.818
After features/support/hooks.rb:330 0.765
After features/support/hooks.rb:100 0.025
Tags: @product @automatic_upgrade
40.916
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.127
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.406
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the signing key used by the Upgrader is outdated 0.113
But a current signing key is available on our website 0.000
When the network is plugged 0.073
And Tor is ready 22.165
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.967
After features/support/hooks.rb:330 0.785
After features/support/hooks.rb:100 0.000