Project Number Date
test_Tails_ISO_20575-disable-cups-browsed 6 04 Oct 2024, 00:55

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:0.477 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:5.172
Before features/support/hooks.rb:269 0.006
Given a computer 0.204
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.056
And I write an old version of the Tails USB image to disk "old" 31.986
When I start Tails from USB drive "old" with network unplugged 1:27.707
Then the boot device has safe access rights 3.149
And Tails is running from USB drive "old" 0.327
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.347
And I unplug USB drive "old" 0.178
After features/support/hooks.rb:326 3.785
After features/support/hooks.rb:100 0.009
Tags: @product
2:3.433
Before features/support/hooks.rb:269 0.005
Given a computer 0.215
And I start Tails from USB drive "old" with network unplugged and I login 1:20.129
Then Tails is running from USB drive "old" 0.331
And I create a persistent partition 31.994
And I take note of which tps features are available 1.639
Then a Tails persistence partition exists on USB drive "old" 0.818
And I shutdown Tails and wait for the computer to power off 8.305
After features/support/hooks.rb:326 0.182
After features/support/hooks.rb:100 0.008
Tags: @product
2:50.960
Before features/support/hooks.rb:269 0.004
Given a computer 0.184
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.152
Then Tails is running from USB drive "old" 0.360
And all tps features are active 1.983
When I write some files expected to persist 1.656
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.291
And all persistence configuration files have safe access rights 0.482
And all persistent directories from the old Tails version have safe access rights 2.524
And I take note of which tps features are available 0.644
And I shutdown Tails and wait for the computer to power off 4.655
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.024
After features/support/hooks.rb:326 0.102
After features/support/hooks.rb:100 0.008
Tags: @product
2:27.305
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.772
And I log in to a new session 18.800
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.153
And I plug USB drive "to_upgrade" 2.369
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.766
Then the running Tails is installed on USB drive "to_upgrade" 17.003
And I unplug USB drive "to_upgrade" 0.229
And I unplug USB drive "__internal" 0.210
After features/support/hooks.rb:326 2.464
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.223
Before features/support/hooks.rb:269 0.006
Given a computer 0.203
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.120
Then all tps features from the old Tails version are active 1.773
And Tails is running from USB drive "to_upgrade" 0.348
And the boot device has safe access rights 2.932
And the expected persistent files created with the old Tails version are present in the filesystem 1.376
And all persistent directories from the old Tails version have safe access rights 2.468
After features/support/hooks.rb:326 0.823
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:43.135
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 13.756
And no SquashFS delta is installed 0.385
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.277
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.305
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.443
When the network is plugged 0.066
And Tor is ready 20.343
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.611
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.573
Given I shutdown Tails and wait for the computer to power off 8.438
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.117
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.201
And the file system changes introduced in version 6.2~testoverlayfs are present 0.306
And only the 6.2~testoverlayfs SquashFS delta is installed 0.079
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.298
# 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.295
When the network is plugged 0.072
And Tor is ready 20.717
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.815
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.280
Given I shutdown Tails and wait for the computer to power off 4.256
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.145
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.318
And the file system changes introduced in version 6.3~testoverlayfs are present 0.509
And only the 6.3~testoverlayfs SquashFS delta is installed 0.087
# 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.403
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.269
When the network is plugged 0.064
And Tor is ready 20.443
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 13.940
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.904
After features/support/hooks.rb:326 0.776
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
35.247
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 10.129
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.449
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the signing key used by the Upgrader is outdated 0.851
But a current signing key is available on our website 0.000
When the network is plugged 0.065
And Tor is ready 17.134
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.558
After features/support/hooks.rb:326 0.678
After features/support/hooks.rb:100 0.000