Project Number Date
test_Tails_ISO_20575-disable-cups-browsed 11 09 Oct 2024, 01:02

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:31.213 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:59.756
Before features/support/hooks.rb:269 0.005
Given a computer 0.194
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" 30.255
When I start Tails from USB drive "old" with network unplugged 1:24.310
Then the boot device has safe access rights 2.892
And Tails is running from USB drive "old" 0.338
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.317
And I unplug USB drive "old" 0.182
After features/support/hooks.rb:326 9.196
After features/support/hooks.rb:100 0.009
Tags: @product
2:0.499
Before features/support/hooks.rb:269 0.006
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login 1:19.057
Then Tails is running from USB drive "old" 0.272
And I create a persistent partition 30.744
And I take note of which tps features are available 1.255
Then a Tails persistence partition exists on USB drive "old" 0.829
And I shutdown Tails and wait for the computer to power off 8.143
After features/support/hooks.rb:326 0.181
After features/support/hooks.rb:100 0.009
Tags: @product
2:56.919
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 with persistence enabled 2:21.027
Then Tails is running from USB drive "old" 0.433
And all tps features are active 1.985
When I write some files expected to persist 1.726
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.192
And all persistence configuration files have safe access rights 0.380
And all persistent directories from the old Tails version have safe access rights 2.303
And I take note of which tps features are available 0.439
And I shutdown Tails and wait for the computer to power off 4.308
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.937
After features/support/hooks.rb:326 0.143
After features/support/hooks.rb:100 0.009
Tags: @product
2:23.215
Before features/support/hooks.rb:269 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.547
And I log in to a new session 17.840
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.662
And I plug USB drive "to_upgrade" 2.352
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.962
Then the running Tails is installed on USB drive "to_upgrade" 17.352
And I unplug USB drive "to_upgrade" 0.227
And I unplug USB drive "__internal" 0.270
After features/support/hooks.rb:326 6.618
After features/support/hooks.rb:100 0.000
Tags: @product
2:9.586
Before features/support/hooks.rb:269 0.006
Given a computer 0.197
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:0.500
Then all tps features from the old Tails version are active 1.605
And Tails is running from USB drive "to_upgrade" 0.288
And the boot device has safe access rights 3.109
And the expected persistent files created with the old Tails version are present in the filesystem 1.463
And all persistent directories from the old Tails version have safe access rights 2.422
After features/support/hooks.rb:326 0.847
After features/support/hooks.rb:100 0.071
Tags: @product @automatic_upgrade
6:24.560
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.161
And no SquashFS delta is installed 0.234
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.284
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.294
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.412
When the network is plugged 0.072
And Tor is ready 19.435
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.474
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.093
Given I shutdown Tails and wait for the computer to power off 8.433
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.810
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.383
And the file system changes introduced in version 6.2~testoverlayfs are present 0.371
And only the 6.2~testoverlayfs SquashFS delta is installed 0.277
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.327
# 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.581
When the network is plugged 0.076
And Tor is ready 20.181
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.870
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.829
Given I shutdown Tails and wait for the computer to power off 4.663
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.998
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 1.937
And the file system changes introduced in version 6.3~testoverlayfs are present 0.488
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.306
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.269
When the network is plugged 0.084
And Tor is ready 19.374
Then the Upgrader considers the system as up-to-date 0.301
# 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.429
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.951
After features/support/hooks.rb:326 0.812
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
36.676
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.014
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.333
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the signing key used by the Upgrader is outdated 0.723
But a current signing key is available on our website 0.000
When the network is plugged 0.064
And Tor is ready 18.987
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.482
After features/support/hooks.rb:326 0.719
After features/support/hooks.rb:100 0.000