Project Number Date
test_Tails_ISO_tca-misc-improvements 6 13 Apr 2025, 18:08

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:15.367 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:6.553
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.206
And I create a 7200 MiB disk named "old" 0.075
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 29.712
When I start Tails from USB drive "old" with network unplugged 1:31.571
Then the boot device has safe access rights 2.961
And Tails is running from USB drive "old" 0.317
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.088
And udev-watchdog is monitoring the correct device 0.308
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:330 7.008
After features/support/hooks.rb:100 0.008
Tags: @product
2:6.995
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.181
And I start Tails from USB drive "old" with network unplugged and I login 1:22.787
Then Tails is running from USB drive "old" 0.354
And I create a persistent partition 31.881
And I take note of which tps features are available 2.741
Then a Tails persistence partition exists on USB drive "old" 0.808
And I shutdown Tails and wait for the computer to power off 8.240
After features/support/hooks.rb:330 0.203
After features/support/hooks.rb:100 0.008
Tags: @product
2:56.465
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.177
Then Tails is running from USB drive "old" 1.060
And all tps features are active 2.456
When I write some files expected to persist 1.666
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.259
And all persistence configuration files have safe access rights 0.423
And all persistent directories from the old Tails version have safe access rights 2.981
And I take note of which tps features are available 0.545
And I shutdown Tails and wait for the computer to power off 6.438
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.269
After features/support/hooks.rb:330 0.130
After features/support/hooks.rb:100 0.009
Tags: @product
2:35.614
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.181
And I log in to a new session 19.415
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.509
And I plug USB drive "to_upgrade" 2.488
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.556
Then the running Tails is installed on USB drive "to_upgrade" 26.055
And I unplug USB drive "to_upgrade" 0.205
And I unplug USB drive "__internal" 0.203
After features/support/hooks.rb:330 2.089
After features/support/hooks.rb:100 0.000
Tags: @product
2:12.707
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.187
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.528
Then all tps features from the old Tails version are active 1.543
And Tails is running from USB drive "to_upgrade" 0.311
And the boot device has safe access rights 3.340
And the expected persistent files created with the old Tails version are present in the filesystem 1.369
And all persistent directories from the old Tails version have safe access rights 2.426
After features/support/hooks.rb:330 1.428
After features/support/hooks.rb:100 0.016
6:38.132
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 15.161
And no SquashFS delta is installed 0.097
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.338
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.313
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.541
When the network is plugged 0.090
And Tor is ready 20.694
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.355
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.276
Given I shutdown Tails and wait for the computer to power off 10.982
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.740
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.411
And the file system changes introduced in version 6.2~testoverlayfs are present 0.373
And only the 6.2~testoverlayfs SquashFS delta is installed 0.085
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.334
# 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.309
When the network is plugged 0.081
And Tor is ready 20.570
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.148
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.376
Given I shutdown Tails and wait for the computer to power off 4.491
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.824
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.633
And the file system changes introduced in version 6.3~testoverlayfs are present 0.528
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.320
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.354
When the network is plugged 0.062
And Tor is ready 18.381
Then the Upgrader considers the system as up-to-date 0.322
# 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.267
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.516
After features/support/hooks.rb:330 0.847
After features/support/hooks.rb:100 0.021
38.898
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.195
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.376
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.106
And the signing key used by the Upgrader is outdated 0.123
But a current signing key is available on our website 0.000
When the network is plugged 0.118
And Tor is ready 19.632
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.345
After features/support/hooks.rb:330 1.077
After features/support/hooks.rb:100 0.000