Project Number Date
test_Tails_ISO_20575-disable-cups-browsed 23 20 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:30.297 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:1.822
Before features/support/hooks.rb:269 0.004
Given a computer 0.182
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 30.076
When I start Tails from USB drive "old" with network unplugged 1:26.501
Then the boot device has safe access rights 3.000
And Tails is running from USB drive "old" 0.313
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.311
And I unplug USB drive "old" 0.184
After features/support/hooks.rb:326 3.490
After features/support/hooks.rb:100 0.008
Tags: @product
2:3.466
Before features/support/hooks.rb:269 0.005
Given a computer 0.189
And I start Tails from USB drive "old" with network unplugged and I login 1:20.423
Then Tails is running from USB drive "old" 0.334
And I create a persistent partition 31.650
And I take note of which tps features are available 1.515
Then a Tails persistence partition exists on USB drive "old" 0.779
And I shutdown Tails and wait for the computer to power off 8.572
After features/support/hooks.rb:326 0.166
After features/support/hooks.rb:100 0.008
Tags: @product
2:43.156
Before features/support/hooks.rb:269 0.005
Given a computer 0.189
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:6.216
Then Tails is running from USB drive "old" 0.602
And all tps features are active 1.981
When I write some files expected to persist 1.730
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.228
And all persistence configuration files have safe access rights 0.339
And all persistent directories from the old Tails version have safe access rights 2.696
And I take note of which tps features are available 0.534
And I shutdown Tails and wait for the computer to power off 4.181
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.455
After features/support/hooks.rb:326 0.100
After features/support/hooks.rb:100 0.007
Tags: @product
2:29.625
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.532
And I log in to a new session 18.393
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.646
And I plug USB drive "to_upgrade" 2.427
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.145
Then the running Tails is installed on USB drive "to_upgrade" 22.049
And I unplug USB drive "to_upgrade" 0.219
And I unplug USB drive "__internal" 0.210
After features/support/hooks.rb:326 2.059
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.503
Before features/support/hooks.rb:269 0.005
Given a computer 0.191
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.492
Then all tps features from the old Tails version are active 1.845
And Tails is running from USB drive "to_upgrade" 0.378
And the boot device has safe access rights 3.041
And the expected persistent files created with the old Tails version are present in the filesystem 1.321
And all persistent directories from the old Tails version have safe access rights 2.231
After features/support/hooks.rb:326 0.880
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:23.180
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.696
And no SquashFS delta is installed 0.187
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.283
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.168
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.243
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.432
When the network is plugged 0.078
And Tor is ready 19.834
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.468
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.083
Given I shutdown Tails and wait for the computer to power off 8.442
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.989
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.414
And the file system changes introduced in version 6.2~testoverlayfs are present 0.300
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.315
# 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.250
When the network is plugged 0.077
And Tor is ready 18.885
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.286
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.607
Given I shutdown Tails and wait for the computer to power off 4.264
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.976
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.109
And the file system changes introduced in version 6.3~testoverlayfs are present 0.470
And only the 6.3~testoverlayfs SquashFS delta is installed 0.096
# 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.324
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.348
When the network is plugged 0.073
And Tor is ready 16.431
Then the Upgrader considers the system as up-to-date 0.387
# 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.548
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.010
After features/support/hooks.rb:326 0.704
After features/support/hooks.rb:100 0.094
Tags: @product @automatic_upgrade
35.542
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 9.825
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.413
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the signing key used by the Upgrader is outdated 0.874
But a current signing key is available on our website 0.000
When the network is plugged 0.071
And Tor is ready 17.780
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.532
After features/support/hooks.rb:326 0.781
After features/support/hooks.rb:100 0.000