Project Number Date
test_Tails_ISO_tca-misc-improvements 4 11 Apr 2025, 18:22

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:56.838 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:3.411
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.194
And I create a 7200 MiB disk named "old" 0.063
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 30.402
When I start Tails from USB drive "old" with network unplugged 1:27.720
Then the boot device has safe access rights 2.919
And Tails is running from USB drive "old" 0.388
And there is no persistence partition on USB drive "old" 0.088
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.303
And I unplug USB drive "old" 0.189
After features/support/hooks.rb:330 6.873
After features/support/hooks.rb:100 0.009
Tags: @product
2:10.105
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.196
And I start Tails from USB drive "old" with network unplugged and I login 1:25.736
Then Tails is running from USB drive "old" 0.348
And I create a persistent partition 33.047
And I take note of which tps features are available 1.764
Then a Tails persistence partition exists on USB drive "old" 0.771
And I shutdown Tails and wait for the computer to power off 8.240
After features/support/hooks.rb:330 0.165
After features/support/hooks.rb:100 0.009
Tags: @product
2:56.747
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.184
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.075
Then Tails is running from USB drive "old" 0.428
And all tps features are active 1.989
When I write some files expected to persist 1.637
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.216
And all persistence configuration files have safe access rights 0.366
And all persistent directories from the old Tails version have safe access rights 2.480
And I take note of which tps features are available 0.411
And I shutdown Tails and wait for the computer to power off 4.481
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.477
After features/support/hooks.rb:330 0.125
After features/support/hooks.rb:100 0.007
Tags: @product
2:37.016
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 10.131
And I log in to a new session 19.545
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.037
And I plug USB drive "to_upgrade" 2.393
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.188
Then the running Tails is installed on USB drive "to_upgrade" 26.281
And I unplug USB drive "to_upgrade" 0.232
And I unplug USB drive "__internal" 0.206
After features/support/hooks.rb:330 2.399
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.492
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.191
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.561
Then all tps features from the old Tails version are active 1.612
And Tails is running from USB drive "to_upgrade" 0.382
And the boot device has safe access rights 3.626
And the expected persistent files created with the old Tails version are present in the filesystem 1.511
And all persistent directories from the old Tails version have safe access rights 2.605
After features/support/hooks.rb:330 0.721
After features/support/hooks.rb:100 0.010
7:13.477
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 12.923
And no SquashFS delta is installed 0.098
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.083
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.090
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.275
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.466
When the network is plugged 0.081
And Tor is ready 24.844
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.679
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.337
Given I shutdown Tails and wait for the computer to power off 10.895
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.994
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 2.283
And the file system changes introduced in version 6.2~testoverlayfs are present 0.339
And only the 6.2~testoverlayfs SquashFS delta is installed 0.078
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.332
# 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.293
When the network is plugged 0.064
And Tor is ready 19.281
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.773
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.587
Given I shutdown Tails and wait for the computer to power off 4.371
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.497
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.574
And the file system changes introduced in version 6.3~testoverlayfs are present 0.706
And only the 6.3~testoverlayfs SquashFS delta is installed 0.078
# 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.419
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.302
When the network is plugged 0.088
And Tor is ready 44.174
Then the Upgrader considers the system as up-to-date 0.292
# 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.590
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.542
After features/support/hooks.rb:330 0.783
After features/support/hooks.rb:100 0.017
37.588
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.344
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.890
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.088
And the signing key used by the Upgrader is outdated 0.082
But a current signing key is available on our website 0.000
When the network is plugged 0.094
And Tor is ready 19.385
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.701
After features/support/hooks.rb:330 0.688
After features/support/hooks.rb:100 0.000