Project Number Date
test_Tails_ISO_20575-disable-cups-browsed 8 06 Oct 2024, 00:40

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 18:28.449 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
1:54.693
Before features/support/hooks.rb:269 0.005
Given a computer 0.185
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 28.542
When I start Tails from USB drive "old" with network unplugged 1:20.984
Then the boot device has safe access rights 2.896
And Tails is running from USB drive "old" 0.303
And there is no persistence partition on USB drive "old" 0.082
And process "udev-watchdog" is running 0.113
And udev-watchdog is monitoring the correct device 0.306
And I unplug USB drive "old" 0.177
After features/support/hooks.rb:326 3.501
After features/support/hooks.rb:100 0.008
Tags: @product
2:0.095
Before features/support/hooks.rb:269 0.005
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login 1:20.466
Then Tails is running from USB drive "old" 0.331
And I create a persistent partition 30.566
And I take note of which tps features are available 1.323
Then a Tails persistence partition exists on USB drive "old" 0.708
And I shutdown Tails and wait for the computer to power off 6.514
After features/support/hooks.rb:326 0.197
After features/support/hooks.rb:100 0.008
Tags: @product
2:45.067
Before features/support/hooks.rb:269 0.005
Given a computer 0.231
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:8.980
Then Tails is running from USB drive "old" 0.329
And all tps features are active 2.028
When I write some files expected to persist 1.642
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.348
And all persistence configuration files have safe access rights 0.378
And all persistent directories from the old Tails version have safe access rights 2.266
And I take note of which tps features are available 0.427
And I shutdown Tails and wait for the computer to power off 4.556
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.878
After features/support/hooks.rb:326 0.120
After features/support/hooks.rb:100 0.008
Tags: @product
2:28.037
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.694
And I log in to a new session 19.649
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.625
And I plug USB drive "to_upgrade" 2.430
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.022
Then the running Tails is installed on USB drive "to_upgrade" 19.144
And I unplug USB drive "to_upgrade" 0.206
And I unplug USB drive "__internal" 0.264
After features/support/hooks.rb:326 0.786
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.340
Before features/support/hooks.rb:269 0.007
Given a computer 0.213
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.372
Then all tps features from the old Tails version are active 1.598
And Tails is running from USB drive "to_upgrade" 0.372
And the boot device has safe access rights 3.180
And the expected persistent files created with the old Tails version are present in the filesystem 1.314
And all persistent directories from the old Tails version have safe access rights 2.287
After features/support/hooks.rb:326 0.726
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:19.089
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.004
And no SquashFS delta is installed 0.092
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.372
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.077
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.279
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.399
When the network is plugged 0.080
And Tor is ready 22.951
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.267
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.744
Given I shutdown Tails and wait for the computer to power off 8.279
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.854
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.038
And the file system changes introduced in version 6.2~testoverlayfs are present 0.267
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.315
# 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.265
When the network is plugged 0.070
And Tor is ready 16.990
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.417
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.506
Given I shutdown Tails and wait for the computer to power off 4.262
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.437
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.121
And the file system changes introduced in version 6.3~testoverlayfs are present 0.535
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.289
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.272
When the network is plugged 0.065
And Tor is ready 19.213
Then the Upgrader considers the system as up-to-date 0.306
# 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 14.019
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.122
After features/support/hooks.rb:326 0.785
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
41.125
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 10.170
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.606
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 0.812
But a current signing key is available on our website 0.000
When the network is plugged 0.075
And Tor is ready 23.073
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.331
After features/support/hooks.rb:326 0.626
After features/support/hooks.rb:100 0.000