Project Number Date
test_Tails_ISO_20575-disable-cups-browsed 7 05 Oct 2024, 00: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 19:4.525 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:1.674
Before features/support/hooks.rb:269 0.005
Given a computer 0.176
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 28.124
When I start Tails from USB drive "old" with network unplugged 1:28.468
Then the boot device has safe access rights 2.829
And Tails is running from USB drive "old" 0.317
And there is no persistence partition on USB drive "old" 0.060
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.315
And I unplug USB drive "old" 0.188
After features/support/hooks.rb:326 3.526
After features/support/hooks.rb:100 0.009
Tags: @product
2:13.258
Before features/support/hooks.rb:269 0.005
Given a computer 0.184
And I start Tails from USB drive "old" with network unplugged and I login 1:29.469
Then Tails is running from USB drive "old" 0.306
And I create a persistent partition 32.364
And I take note of which tps features are available 1.586
Then a Tails persistence partition exists on USB drive "old" 0.792
And I shutdown Tails and wait for the computer to power off 8.554
After features/support/hooks.rb:326 0.188
After features/support/hooks.rb:100 0.008
Tags: @product
2:56.529
Before features/support/hooks.rb:269 0.005
Given a computer 0.189
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.950
Then Tails is running from USB drive "old" 1.022
And all tps features are active 1.876
When I write some files expected to persist 1.590
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.261
And all persistence configuration files have safe access rights 1.241
And all persistent directories from the old Tails version have safe access rights 2.881
And I take note of which tps features are available 0.458
And I shutdown Tails and wait for the computer to power off 4.141
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.916
After features/support/hooks.rb:326 0.131
After features/support/hooks.rb:100 0.009
Tags: @product
2:22.383
Before features/support/hooks.rb:269 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.366
And I log in to a new session 18.654
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.491
And I plug USB drive "to_upgrade" 2.345
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.836
Then the running Tails is installed on USB drive "to_upgrade" 17.268
And I unplug USB drive "to_upgrade" 0.213
And I unplug USB drive "__internal" 0.208
After features/support/hooks.rb:326 2.311
After features/support/hooks.rb:100 0.000
Tags: @product
2:10.527
Before features/support/hooks.rb:269 0.005
Given a computer 0.182
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.976
Then all tps features from the old Tails version are active 1.478
And Tails is running from USB drive "to_upgrade" 0.362
And the boot device has safe access rights 2.928
And the expected persistent files created with the old Tails version are present in the filesystem 1.340
And all persistent directories from the old Tails version have safe access rights 2.258
After features/support/hooks.rb:326 0.624
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
6:43.364
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.132
And no SquashFS delta is installed 0.089
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.303
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.280
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.475
When the network is plugged 0.076
And Tor is ready 20.070
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.433
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.994
Given I shutdown Tails and wait for the computer to power off 8.571
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.624
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.034
And the file system changes introduced in version 6.2~testoverlayfs are present 0.355
And only the 6.2~testoverlayfs SquashFS delta is installed 0.080
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.294
# 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.294
When the network is plugged 0.058
And Tor is ready 45.413
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.578
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.606
Given I shutdown Tails and wait for the computer to power off 4.591
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.759
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 1.954
And the file system changes introduced in version 6.3~testoverlayfs are present 0.443
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.317
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.278
When the network is plugged 0.091
And Tor is ready 21.681
Then the Upgrader considers the system as up-to-date 0.296
# 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 13.935
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.092
After features/support/hooks.rb:326 0.686
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
36.787
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.562
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.294
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 0.677
But a current signing key is available on our website 0.000
When the network is plugged 0.068
And Tor is ready 16.724
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.398
After features/support/hooks.rb:326 0.727
After features/support/hooks.rb:100 0.000