Project Number Date
test_Tails_ISO_20575-disable-cups-browsed 20 17 Oct 2024, 00:58

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:20.430 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:53.432
Before features/support/hooks.rb:269 0.004
Given a computer 0.173
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 27.355
When I start Tails from USB drive "old" with network unplugged 1:20.840
Then the boot device has safe access rights 3.024
And Tails is running from USB drive "old" 0.331
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.085
And udev-watchdog is monitoring the correct device 0.277
And I unplug USB drive "old" 0.185
After features/support/hooks.rb:326 3.505
After features/support/hooks.rb:100 0.012
Tags: @product
2:4.457
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:23.116
Then Tails is running from USB drive "old" 0.356
And I create a persistent partition 30.236
And I take note of which tps features are available 1.246
Then a Tails persistence partition exists on USB drive "old" 0.727
And I shutdown Tails and wait for the computer to power off 8.589
After features/support/hooks.rb:326 0.131
After features/support/hooks.rb:100 0.008
Tags: @product
2:50.846
Before features/support/hooks.rb:269 0.004
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.832
Then Tails is running from USB drive "old" 0.305
And all tps features are active 2.013
When I write some files expected to persist 1.813
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.304
And all persistence configuration files have safe access rights 0.394
And all persistent directories from the old Tails version have safe access rights 2.386
And I take note of which tps features are available 0.410
And I shutdown Tails and wait for the computer to power off 4.282
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.907
After features/support/hooks.rb:326 0.143
After features/support/hooks.rb:100 0.008
Tags: @product
2:23.148
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.617
And I log in to a new session 18.130
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.537
And I plug USB drive "to_upgrade" 2.468
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.436
Then the running Tails is installed on USB drive "to_upgrade" 16.557
And I unplug USB drive "to_upgrade" 0.202
And I unplug USB drive "__internal" 0.198
After features/support/hooks.rb:326 6.929
After features/support/hooks.rb:100 0.000
Tags: @product
2:10.033
Before features/support/hooks.rb:269 0.005
Given a computer 0.213
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:0.376
Then all tps features from the old Tails version are active 1.727
And Tails is running from USB drive "to_upgrade" 0.312
And the boot device has safe access rights 3.406
And the expected persistent files created with the old Tails version are present in the filesystem 1.496
And all persistent directories from the old Tails version have safe access rights 2.500
After features/support/hooks.rb:326 0.758
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:19.555
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 13.400
And no SquashFS delta is installed 0.110
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.901
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.265
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.456
When the network is plugged 0.070
And Tor is ready 25.911
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.354
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.215
Given I shutdown Tails and wait for the computer to power off 10.398
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.437
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.110
And the file system changes introduced in version 6.2~testoverlayfs are present 0.287
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.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.281
When the network is plugged 0.134
And Tor is ready 17.731
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.268
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.510
Given I shutdown Tails and wait for the computer to power off 4.639
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.913
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.329
And the file system changes introduced in version 6.3~testoverlayfs are present 0.511
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.341
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.273
When the network is plugged 0.068
And Tor is ready 17.612
Then the Upgrader considers the system as up-to-date 0.334
# 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.199
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.943
After features/support/hooks.rb:326 0.773
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
38.957
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.629
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.718
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.080
And the signing key used by the Upgrader is outdated 1.331
But a current signing key is available on our website 0.000
When the network is plugged 0.063
And Tor is ready 21.145
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.989
After features/support/hooks.rb:326 1.418
After features/support/hooks.rb:100 0.000