Project Number Date
test_Tails_ISO_tca-misc-improvements 8 15 Apr 2025, 18: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 23:48.241 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:31.720
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.210
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 31.603
When I start Tails from USB drive "old" with network unplugged 1:54.891
Then the boot device has safe access rights 2.970
And Tails is running from USB drive "old" 0.301
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.089
And udev-watchdog is monitoring the correct device 0.311
And I unplug USB drive "old" 0.190
After features/support/hooks.rb:330 0.821
After features/support/hooks.rb:100 0.009
Tags: @product
2:11.495
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.179
And I start Tails from USB drive "old" with network unplugged and I login 1:27.572
Then Tails is running from USB drive "old" 0.377
And I create a persistent partition 32.200
And I take note of which tps features are available 1.998
Then a Tails persistence partition exists on USB drive "old" 0.847
And I shutdown Tails and wait for the computer to power off 8.319
After features/support/hooks.rb:330 0.178
After features/support/hooks.rb:100 0.008
Tags: @product
2:53.404
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.223
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.061
Then Tails is running from USB drive "old" 0.514
And all tps features are active 2.203
When I write some files expected to persist 1.762
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.224
And all persistence configuration files have safe access rights 0.442
And all persistent directories from the old Tails version have safe access rights 2.603
And I take note of which tps features are available 0.529
And I shutdown Tails and wait for the computer to power off 4.469
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.369
After features/support/hooks.rb:330 0.139
After features/support/hooks.rb:100 0.007
Tags: @product
2:39.964
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.737
And I log in to a new session 19.869
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.552
And I plug USB drive "to_upgrade" 2.407
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.943
Then the running Tails is installed on USB drive "to_upgrade" 28.026
And I unplug USB drive "to_upgrade" 0.218
And I unplug USB drive "__internal" 0.209
After features/support/hooks.rb:330 3.545
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.804
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.199
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.910
Then all tps features from the old Tails version are active 1.570
And Tails is running from USB drive "to_upgrade" 0.374
And the boot device has safe access rights 3.524
And the expected persistent files created with the old Tails version are present in the filesystem 1.510
And all persistent directories from the old Tails version have safe access rights 2.714
After features/support/hooks.rb:330 2.487
After features/support/hooks.rb:100 0.009
10:2.221
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 13.692
And no SquashFS delta is installed 0.273
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.834
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.102
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.373
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.565
When the network is plugged 0.093
And Tor is ready 21.190
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 10.967
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.511
Given I shutdown Tails and wait for the computer to power off 1:31.152
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.903
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.261
And the file system changes introduced in version 6.2~testoverlayfs are present 0.341
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.316
# 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.332
When the network is plugged 0.070
And Tor is ready 21.539
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.539
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.268
Given I shutdown Tails and wait for the computer to power off 1:4.121
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:21.050
Then Tails is running version 6.3~testoverlayfs 0.024
And all tps features are active 4.186
And the file system changes introduced in version 6.3~testoverlayfs are present 0.824
And only the 6.3~testoverlayfs SquashFS delta is installed 0.108
# 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.460
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.429
When the network is plugged 0.088
And Tor is ready 50.875
Then the Upgrader considers the system as up-to-date 0.341
# 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.249
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.048
After features/support/hooks.rb:330 0.852
After features/support/hooks.rb:100 0.021
1:8.630
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 17.196
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.122
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.083
And the signing key used by the Upgrader is outdated 0.076
But a current signing key is available on our website 0.000
When the network is plugged 0.302
And Tor is ready 49.259
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.588
After features/support/hooks.rb:330 0.691
After features/support/hooks.rb:100 0.000