Project Number Date
test_Tails_ISO_20575-disable-cups-browsed 25 22 Oct 2024, 00:38

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:18.311 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:0.422
Before features/support/hooks.rb:269 0.005
Given a computer 0.181
And I create a 7200 MiB disk named "old" 0.055
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 29.215
When I start Tails from USB drive "old" with network unplugged 1:26.007
Then the boot device has safe access rights 2.891
And Tails is running from USB drive "old" 0.330
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.328
And I unplug USB drive "old" 0.179
After features/support/hooks.rb:326 7.079
After features/support/hooks.rb:100 0.018
Tags: @product
2:5.000
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 1:20.693
Then Tails is running from USB drive "old" 0.320
And I create a persistent partition 32.878
And I take note of which tps features are available 1.449
Then a Tails persistence partition exists on USB drive "old" 0.857
And I shutdown Tails and wait for the computer to power off 8.615
After features/support/hooks.rb:326 0.181
After features/support/hooks.rb:100 0.008
Tags: @product
2:48.062
Before features/support/hooks.rb:269 0.005
Given a computer 0.197
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:10.970
Then Tails is running from USB drive "old" 0.922
And all tps features are active 2.024
When I write some files expected to persist 1.858
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.240
And all persistence configuration files have safe access rights 0.360
And all persistent directories from the old Tails version have safe access rights 2.815
And I take note of which tps features are available 0.465
And I shutdown Tails and wait for the computer to power off 4.297
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.909
After features/support/hooks.rb:326 0.132
After features/support/hooks.rb:100 0.009
Tags: @product
2:28.235
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.364
And I log in to a new session 17.476
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.761
And I plug USB drive "to_upgrade" 2.408
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.004
Then the running Tails is installed on USB drive "to_upgrade" 21.790
And I unplug USB drive "to_upgrade" 0.224
And I unplug USB drive "__internal" 0.205
After features/support/hooks.rb:326 3.539
After features/support/hooks.rb:100 0.000
Tags: @product
2:6.062
Before features/support/hooks.rb:269 0.006
Given a computer 0.191
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:57.053
Then all tps features from the old Tails version are active 1.605
And Tails is running from USB drive "to_upgrade" 0.308
And the boot device has safe access rights 2.927
And the expected persistent files created with the old Tails version are present in the filesystem 1.604
And all persistent directories from the old Tails version have safe access rights 2.371
After features/support/hooks.rb:326 0.734
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:13.658
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.406
And no SquashFS delta is installed 0.074
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.278
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.296
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.426
When the network is plugged 0.083
And Tor is ready 21.872
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.218
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.105
Given I shutdown Tails and wait for the computer to power off 8.339
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.559
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.058
And the file system changes introduced in version 6.2~testoverlayfs are present 0.375
And only the 6.2~testoverlayfs SquashFS delta is installed 0.092
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.391
# 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.292
When the network is plugged 0.081
And Tor is ready 18.404
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.940
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.324
Given I shutdown Tails and wait for the computer to power off 4.549
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.097
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.128
And the file system changes introduced in version 6.3~testoverlayfs are present 0.458
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.309
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.458
When the network is plugged 0.085
And Tor is ready 20.687
Then the Upgrader considers the system as up-to-date 0.307
# 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.803
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.003
After features/support/hooks.rb:326 0.705
After features/support/hooks.rb:100 0.036
Tags: @product @automatic_upgrade
36.869
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.810
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.317
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the signing key used by the Upgrader is outdated 0.811
But a current signing key is available on our website 0.000
When the network is plugged 0.072
And Tor is ready 19.471
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.316
After features/support/hooks.rb:326 0.679
After features/support/hooks.rb:100 0.000