Project Number Date
test_Tails_ISO_20575-disable-cups-browsed 9 07 Oct 2024, 02:42

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:13.313 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:3.153
Before features/support/hooks.rb:269 0.005
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" 28.919
When I start Tails from USB drive "old" with network unplugged 1:29.131
Then the boot device has safe access rights 2.852
And Tails is running from USB drive "old" 0.341
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.095
And udev-watchdog is monitoring the correct device 0.290
And I unplug USB drive "old" 0.179
After features/support/hooks.rb:326 3.549
After features/support/hooks.rb:100 0.008
Tags: @product
2:2.765
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.920
Then Tails is running from USB drive "old" 0.309
And I create a persistent partition 30.949
And I take note of which tps features are available 1.361
Then a Tails persistence partition exists on USB drive "old" 0.775
And I shutdown Tails and wait for the computer to power off 8.264
After features/support/hooks.rb:326 0.150
After features/support/hooks.rb:100 0.009
Tags: @product
2:56.302
Before features/support/hooks.rb:269 0.005
Given a computer 0.178
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.634
Then Tails is running from USB drive "old" 1.684
And all tps features are active 1.914
When I write some files expected to persist 1.513
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.197
And all persistence configuration files have safe access rights 0.554
And all persistent directories from the old Tails version have safe access rights 3.718
And I take note of which tps features are available 0.482
And I shutdown Tails and wait for the computer to power off 4.532
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.890
After features/support/hooks.rb:326 0.084
After features/support/hooks.rb:100 0.010
Tags: @product
2:24.754
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 11.012
And I log in to a new session 19.213
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.589
And I plug USB drive "to_upgrade" 2.386
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.052
Then the running Tails is installed on USB drive "to_upgrade" 17.071
And I unplug USB drive "to_upgrade" 0.208
And I unplug USB drive "__internal" 0.218
After features/support/hooks.rb:326 2.927
After features/support/hooks.rb:100 0.000
Tags: @product
2:6.620
Before features/support/hooks.rb:269 0.006
Given a computer 0.183
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:57.863
Then all tps features from the old Tails version are active 1.534
And Tails is running from USB drive "to_upgrade" 0.307
And the boot device has safe access rights 2.960
And the expected persistent files created with the old Tails version are present in the filesystem 1.414
And all persistent directories from the old Tails version have safe access rights 2.355
After features/support/hooks.rb:326 0.891
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:4.688
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.461
And no SquashFS delta is installed 0.105
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.263
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.288
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.432
When the network is plugged 0.077
And Tor is ready 22.917
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.465
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.016
Given I shutdown Tails and wait for the computer to power off 8.846
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.054
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.076
And the file system changes introduced in version 6.2~testoverlayfs are present 0.278
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.439
# 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.251
When the network is plugged 0.097
And Tor is ready 17.110
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.279
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.446
Given I shutdown Tails and wait for the computer to power off 4.661
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.936
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.081
And the file system changes introduced in version 6.3~testoverlayfs are present 0.512
And only the 6.3~testoverlayfs SquashFS delta is installed 0.066
# 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.292
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.245
When the network is plugged 0.088
And Tor is ready 17.920
Then the Upgrader considers the system as up-to-date 0.343
# 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.429
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.042
After features/support/hooks.rb:326 0.770
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
35.030
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 9.994
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.049
And the signing key used by the Upgrader is outdated 0.808
But a current signing key is available on our website 0.000
When the network is plugged 0.062
And Tor is ready 17.438
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.377
After features/support/hooks.rb:326 0.977
After features/support/hooks.rb:100 0.000