Project Number Date
test_Tails_ISO_20575-disable-cups-browsed 16 13 Oct 2024, 00:57

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:23.582 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:56.137
Before features/support/hooks.rb:269 0.003
Given a computer 0.188
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 29.517
When I start Tails from USB drive "old" with network unplugged 1:21.658
Then the boot device has safe access rights 2.740
And Tails is running from USB drive "old" 0.309
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.086
And udev-watchdog is monitoring the correct device 0.282
And I unplug USB drive "old" 0.190
After features/support/hooks.rb:326 6.979
After features/support/hooks.rb:100 0.008
Tags: @product
2:7.505
Before features/support/hooks.rb:269 0.005
Given a computer 0.188
And I start Tails from USB drive "old" with network unplugged and I login 1:24.665
Then Tails is running from USB drive "old" 0.301
And I create a persistent partition 32.066
And I take note of which tps features are available 1.278
Then a Tails persistence partition exists on USB drive "old" 0.785
And I shutdown Tails and wait for the computer to power off 8.219
After features/support/hooks.rb:326 0.177
After features/support/hooks.rb:100 0.008
Tags: @product
2:42.052
Before features/support/hooks.rb:269 0.005
Given a computer 0.180
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:6.030
Then Tails is running from USB drive "old" 0.293
And all tps features are active 2.041
When I write some files expected to persist 1.568
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.208
And all persistence configuration files have safe access rights 0.384
And all persistent directories from the old Tails version have safe access rights 2.515
And I take note of which tps features are available 0.494
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" 24.052
After features/support/hooks.rb:326 0.142
After features/support/hooks.rb:100 0.008
Tags: @product
2:22.318
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.814
And I log in to a new session 17.216
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.495
And I plug USB drive "to_upgrade" 2.370
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.959
Then the running Tails is installed on USB drive "to_upgrade" 16.030
And I unplug USB drive "to_upgrade" 0.191
And I unplug USB drive "__internal" 0.239
After features/support/hooks.rb:326 3.200
After features/support/hooks.rb:100 0.000
Tags: @product
2:9.629
Before features/support/hooks.rb:269 0.005
Given a computer 0.223
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:0.722
Then all tps features from the old Tails version are active 1.612
And Tails is running from USB drive "to_upgrade" 0.295
And the boot device has safe access rights 3.178
And the expected persistent files created with the old Tails version are present in the filesystem 1.402
And all persistent directories from the old Tails version have safe access rights 2.194
After features/support/hooks.rb:326 0.943
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:28.338
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 11.618
And no SquashFS delta is installed 0.072
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.650
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.289
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.416
When the network is plugged 0.095
And Tor is ready 20.911
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.817
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.311
Given I shutdown Tails and wait for the computer to power off 10.497
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.391
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.093
And the file system changes introduced in version 6.2~testoverlayfs are present 0.301
And only the 6.2~testoverlayfs SquashFS delta is installed 0.096
# 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.255
When the network is plugged 0.071
And Tor is ready 18.387
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.422
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.349
Given I shutdown Tails and wait for the computer to power off 4.314
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.757
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.966
And the file system changes introduced in version 6.3~testoverlayfs are present 0.590
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.482
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.284
When the network is plugged 0.074
And Tor is ready 19.442
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.718
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.898
After features/support/hooks.rb:326 0.729
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
37.599
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.050
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.374
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the signing key used by the Upgrader is outdated 0.734
But a current signing key is available on our website 0.000
When the network is plugged 0.093
And Tor is ready 18.554
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.745
After features/support/hooks.rb:326 0.672
After features/support/hooks.rb:100 0.000