Project Number Date
test_Tails_ISO_20575-disable-cups-browsed 5 03 Oct 2024, 01:14

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:47.500 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:16.727
Before features/support/hooks.rb:269 0.011
Given a computer 0.261
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 33.276
When I start Tails from USB drive "old" with network unplugged 1:37.621
Then the boot device has safe access rights 3.256
And Tails is running from USB drive "old" 0.388
And there is no persistence partition on USB drive "old" 0.088
And process "udev-watchdog" is running 0.128
And udev-watchdog is monitoring the correct device 0.368
And I unplug USB drive "old" 0.230
After features/support/hooks.rb:326 3.761
After features/support/hooks.rb:100 0.011
Tags: @product
2:12.328
Before features/support/hooks.rb:269 0.006
Given a computer 0.241
And I start Tails from USB drive "old" with network unplugged and I login 1:27.725
Then Tails is running from USB drive "old" 0.387
And I create a persistent partition 31.903
And I take note of which tps features are available 2.355
Then a Tails persistence partition exists on USB drive "old" 0.995
And I shutdown Tails and wait for the computer to power off 8.719
After features/support/hooks.rb:326 0.205
After features/support/hooks.rb:100 0.009
Tags: @product
2:54.273
Before features/support/hooks.rb:269 0.006
Given a computer 0.240
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.897
Then Tails is running from USB drive "old" 0.606
And all tps features are active 2.516
When I write some files expected to persist 2.055
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.222
And all persistence configuration files have safe access rights 0.468
And all persistent directories from the old Tails version have safe access rights 2.774
And I take note of which tps features are available 0.523
And I shutdown Tails and wait for the computer to power off 4.704
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.262
After features/support/hooks.rb:326 0.131
After features/support/hooks.rb:100 0.010
Tags: @product
2:37.190
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 12.140
And I log in to a new session 19.559
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.990
And I plug USB drive "to_upgrade" 2.435
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.810
Then the running Tails is installed on USB drive "to_upgrade" 25.796
And I unplug USB drive "to_upgrade" 0.231
And I unplug USB drive "__internal" 0.227
After features/support/hooks.rb:326 1.923
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.667
Before features/support/hooks.rb:269 0.006
Given a computer 0.186
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.875
Then all tps features from the old Tails version are active 1.592
And Tails is running from USB drive "to_upgrade" 0.287
And the boot device has safe access rights 3.543
And the expected persistent files created with the old Tails version are present in the filesystem 2.521
And all persistent directories from the old Tails version have safe access rights 2.661
After features/support/hooks.rb:326 1.028
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:46.832
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.368
And no SquashFS delta is installed 0.104
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.403
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.079
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.396
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.561
When the network is plugged 0.124
And Tor is ready 23.051
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.114
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.261
Given I shutdown Tails and wait for the computer to power off 8.903
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:18.105
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.438
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.087
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.340
# 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.252
When the network is plugged 0.065
And Tor is ready 19.605
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.646
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.043
Given I shutdown Tails and wait for the computer to power off 4.429
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.164
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.613
And the file system changes introduced in version 6.3~testoverlayfs are present 0.498
And only the 6.3~testoverlayfs SquashFS delta is installed 0.086
# 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.319
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.337
When the network is plugged 0.075
And Tor is ready 20.525
Then the Upgrader considers the system as up-to-date 0.346
# 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.996
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.084
After features/support/hooks.rb:326 0.794
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
40.479
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.043
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.683
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the signing key used by the Upgrader is outdated 0.965
But a current signing key is available on our website 0.000
When the network is plugged 0.083
And Tor is ready 19.882
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.747
After features/support/hooks.rb:326 0.684
After features/support/hooks.rb:100 0.000