Project Number Date
test_Tails_ISO_tca-misc-improvements 18 25 Apr 2025, 18:47

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:28.950 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:19.458
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.194
And I create a 7200 MiB disk named "old" 0.053
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 32.837
When I start Tails from USB drive "old" with network unplugged 1:41.096
Then the boot device has safe access rights 3.199
And Tails is running from USB drive "old" 0.316
And there is no persistence partition on USB drive "old" 0.089
And process "udev-watchdog" is running 0.114
And udev-watchdog is monitoring the correct device 0.296
And I unplug USB drive "old" 0.211
After features/support/hooks.rb:330 7.202
After features/support/hooks.rb:100 0.008
Tags: @product
2:11.684
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login 1:30.029
Then Tails is running from USB drive "old" 0.353
And I create a persistent partition 31.804
And I take note of which tps features are available 2.130
Then a Tails persistence partition exists on USB drive "old" 0.789
And I shutdown Tails and wait for the computer to power off 6.373
After features/support/hooks.rb:330 0.155
After features/support/hooks.rb:100 0.009
Tags: @product
3:4.917
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.210
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:23.798
Then Tails is running from USB drive "old" 0.753
And all tps features are active 2.237
When I write some files expected to persist 2.814
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.247
And all persistence configuration files have safe access rights 0.377
And all persistent directories from the old Tails version have safe access rights 2.945
And I take note of which tps features are available 0.433
And I shutdown Tails and wait for the computer to power off 5.755
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.344
After features/support/hooks.rb:330 0.212
After features/support/hooks.rb:100 0.009
Tags: @product
2:36.963
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 12.284
And I log in to a new session 20.514
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.963
And I plug USB drive "to_upgrade" 2.416
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.251
Then the running Tails is installed on USB drive "to_upgrade" 23.134
And I unplug USB drive "to_upgrade" 0.191
And I unplug USB drive "__internal" 0.207
After features/support/hooks.rb:330 0.967
After features/support/hooks.rb:100 0.000
Tags: @product
2:22.349
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.200
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.411
Then all tps features from the old Tails version are active 1.807
And Tails is running from USB drive "to_upgrade" 0.345
And the boot device has safe access rights 3.705
And the expected persistent files created with the old Tails version are present in the filesystem 1.904
And all persistent directories from the old Tails version have safe access rights 2.973
After features/support/hooks.rb:330 1.238
After features/support/hooks.rb:100 0.011
7:12.729
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.513
And no SquashFS delta is installed 0.425
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.354
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.161
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.331
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.474
When the network is plugged 0.066
And Tor is ready 24.542
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.007
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.762
Given I shutdown Tails and wait for the computer to power off 11.196
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:17.635
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 5.109
And the file system changes introduced in version 6.2~testoverlayfs are present 0.357
And only the 6.2~testoverlayfs SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.312
# 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.327
When the network is plugged 0.093
And Tor is ready 19.015
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.114
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.100
Given I shutdown Tails and wait for the computer to power off 4.634
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.985
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.103
And the file system changes introduced in version 6.3~testoverlayfs are present 1.136
And only the 6.3~testoverlayfs SquashFS delta is installed 0.762
# 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.417
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.293
When the network is plugged 0.071
And Tor is ready 21.338
Then the Upgrader considers the system as up-to-date 0.499
# 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.896
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.581
After features/support/hooks.rb:330 0.789
After features/support/hooks.rb:100 0.023
40.847
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.496
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.459
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.102
And the signing key used by the Upgrader is outdated 0.117
But a current signing key is available on our website 0.000
When the network is plugged 0.086
And Tor is ready 20.923
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.662
After features/support/hooks.rb:330 0.677
After features/support/hooks.rb:100 0.000