Project Number Date
test_Tails_ISO_20575-disable-cups-browsed 19 16 Oct 2024, 00:48

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:10.234 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:57.379
Before features/support/hooks.rb:269 0.004
Given a computer 0.186
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 27.975
When I start Tails from USB drive "old" with network unplugged 1:24.346
Then the boot device has safe access rights 2.821
And Tails is running from USB drive "old" 0.311
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.107
And udev-watchdog is monitoring the correct device 0.290
And I unplug USB drive "old" 0.183
After features/support/hooks.rb:326 3.578
After features/support/hooks.rb:100 0.009
Tags: @product
2:1.673
Before features/support/hooks.rb:269 0.006
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login 1:19.251
Then Tails is running from USB drive "old" 0.409
And I create a persistent partition 31.442
And I take note of which tps features are available 1.404
Then a Tails persistence partition exists on USB drive "old" 0.796
And I shutdown Tails and wait for the computer to power off 8.182
After features/support/hooks.rb:326 0.178
After features/support/hooks.rb:100 0.009
Tags: @product
2:50.871
Before features/support/hooks.rb:269 0.005
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.415
Then Tails is running from USB drive "old" 0.331
And all tps features are active 1.873
When I write some files expected to persist 4.477
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.213
And all persistence configuration files have safe access rights 0.371
And all persistent directories from the old Tails version have safe access rights 2.336
And I take note of which tps features are available 0.452
And I shutdown Tails and wait for the computer to power off 4.279
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.925
After features/support/hooks.rb:326 0.119
After features/support/hooks.rb:100 0.009
Tags: @product
2:27.296
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.568
And I log in to a new session 18.063
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.623
And I plug USB drive "to_upgrade" 2.694
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.640
Then the running Tails is installed on USB drive "to_upgrade" 20.276
And I unplug USB drive "to_upgrade" 0.217
And I unplug USB drive "__internal" 0.212
After features/support/hooks.rb:326 5.341
After features/support/hooks.rb:100 0.000
Tags: @product
2:5.546
Before features/support/hooks.rb:269 0.006
Given a computer 0.193
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:56.435
Then all tps features from the old Tails version are active 1.648
And Tails is running from USB drive "to_upgrade" 0.369
And the boot device has safe access rights 2.997
And the expected persistent files created with the old Tails version are present in the filesystem 1.446
And all persistent directories from the old Tails version have safe access rights 2.454
After features/support/hooks.rb:326 1.045
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:12.342
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.540
And no SquashFS delta is installed 0.069
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.298
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.445
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.444
When the network is plugged 0.190
And Tor is ready 17.123
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.430
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.186
Given I shutdown Tails and wait for the computer to power off 8.782
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.187
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.012
And the file system changes introduced in version 6.2~testoverlayfs are present 0.292
And only the 6.2~testoverlayfs SquashFS delta is installed 0.058
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.310
# 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.269
When the network is plugged 0.072
And Tor is ready 19.175
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.983
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.707
Given I shutdown Tails and wait for the computer to power off 4.251
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.281
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.134
And the file system changes introduced in version 6.3~testoverlayfs are present 0.466
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.333
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.260
When the network is plugged 0.061
And Tor is ready 17.307
Then the Upgrader considers the system as up-to-date 10.756
# 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.952
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.797
After features/support/hooks.rb:326 0.694
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
35.124
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 9.742
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.528
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 1.157
But a current signing key is available on our website 0.000
When the network is plugged 0.077
And Tor is ready 18.652
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.911
After features/support/hooks.rb:326 0.746
After features/support/hooks.rb:100 0.000