Project Number Date
test_Tails_ISO_tca-misc-improvements 5 12 Apr 2025, 18:02

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 20:40.748 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:2.932
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.211
And I create a 7200 MiB disk named "old" 0.066
And I plug USB drive "old" 1.056
And I write an old version of the Tails USB image to disk "old" 29.750
When I start Tails from USB drive "old" with network unplugged 1:27.709
Then the boot device has safe access rights 3.084
And Tails is running from USB drive "old" 0.333
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.336
And I unplug USB drive "old" 0.209
After features/support/hooks.rb:330 3.781
After features/support/hooks.rb:100 0.010
Tags: @product
2:13.249
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 "old" with network unplugged and I login 1:29.819
Then Tails is running from USB drive "old" 0.320
And I create a persistent partition 31.410
And I take note of which tps features are available 1.946
Then a Tails persistence partition exists on USB drive "old" 0.855
And I shutdown Tails and wait for the computer to power off 8.686
After features/support/hooks.rb:330 0.208
After features/support/hooks.rb:100 0.013
Tags: @product
2:55.616
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.242
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.192
Then Tails is running from USB drive "old" 0.819
And all tps features are active 1.899
When I write some files expected to persist 1.601
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.214
And all persistence configuration files have safe access rights 0.377
And all persistent directories from the old Tails version have safe access rights 3.192
And I take note of which tps features are available 0.508
And I shutdown Tails and wait for the computer to power off 4.295
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.272
After features/support/hooks.rb:330 0.113
After features/support/hooks.rb:100 0.009
Tags: @product
2:31.894
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.584
And I log in to a new session 21.088
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.533
And I plug USB drive "to_upgrade" 2.452
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.332
Then the running Tails is installed on USB drive "to_upgrade" 21.484
And I unplug USB drive "to_upgrade" 0.210
And I unplug USB drive "__internal" 0.206
After features/support/hooks.rb:330 3.544
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.913
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.401
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.701
Then all tps features from the old Tails version are active 1.852
And Tails is running from USB drive "to_upgrade" 0.376
And the boot device has safe access rights 4.029
And the expected persistent files created with the old Tails version are present in the filesystem 1.641
And all persistent directories from the old Tails version have safe access rights 2.911
After features/support/hooks.rb:330 1.437
After features/support/hooks.rb:100 0.012
7:57.932
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.101
And no SquashFS delta is installed 0.706
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.483
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.293
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.535
When the network is plugged 0.064
And Tor is ready 22.750
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.022
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.371
Given I shutdown Tails and wait for the computer to power off 1:28.817
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.367
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.276
And the file system changes introduced in version 6.2~testoverlayfs are present 0.321
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.340
When the network is plugged 0.078
And Tor is ready 18.896
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.691
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.118
Given I shutdown Tails and wait for the computer to power off 4.287
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.491
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.055
And the file system changes introduced in version 6.3~testoverlayfs are present 0.497
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.307
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.284
When the network is plugged 0.078
And Tor is ready 16.412
Then the Upgrader considers the system as up-to-date 0.332
# 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 15.781
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.607
After features/support/hooks.rb:330 0.837
After features/support/hooks.rb:100 0.022
40.210
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 10.008
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.403
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.090
And the signing key used by the Upgrader is outdated 0.103
But a current signing key is available on our website 0.000
When the network is plugged 0.150
And Tor is ready 22.119
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.334
After features/support/hooks.rb:330 0.685
After features/support/hooks.rb:100 0.000