Project Number Date
test_Tails_ISO_devel 3416 05 Jun 2024, 12:45

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:36.625 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:4.619
Before features/support/hooks.rb:269 0.012
Given a computer 0.237
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 29.262
When I start Tails from USB drive "old" with network unplugged 1:29.931
Then the boot device has safe access rights 3.103
And Tails is running from USB drive "old" 0.303
And there is no persistence partition on USB drive "old" 0.078
And process "udev-watchdog" is running 0.095
And udev-watchdog is monitoring the correct device 0.319
And I unplug USB drive "old" 0.187
After features/support/hooks.rb:315 3.780
After features/support/hooks.rb:100 0.009
Tags: @product
2:15.518
Before features/support/hooks.rb:269 0.006
Given a computer 0.221
And I start Tails from USB drive "old" with network unplugged and I login 1:29.389
Then Tails is running from USB drive "old" 0.360
And I create a persistent partition 34.386
And I take note of which tps features are available 2.006
Then a Tails persistence partition exists on USB drive "old" 0.812
And I shutdown Tails and wait for the computer to power off 8.340
After features/support/hooks.rb:315 0.191
After features/support/hooks.rb:100 0.010
Tags: @product
2:43.630
Before features/support/hooks.rb:269 0.005
Given a computer 0.217
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:6.696
Then Tails is running from USB drive "old" 0.389
And all tps features are active 2.088
When I write some files expected to persist 1.755
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.237
And all persistence configuration files have safe access rights 0.353
And all persistent directories from the old Tails version have safe access rights 2.730
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.144
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.533
After features/support/hooks.rb:315 0.111
After features/support/hooks.rb:100 0.010
Tags: @product
2:30.798
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.404
And I log in to a new session 19.658
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.425
And I plug USB drive "to_upgrade" 2.411
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.904
Then the running Tails is installed on USB drive "to_upgrade" 17.573
And I unplug USB drive "to_upgrade" 0.216
And I unplug USB drive "__internal" 0.203
After features/support/hooks.rb:315 0.879
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.530
Before features/support/hooks.rb:269 0.007
Given a computer 0.231
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.537
Then all tps features from the old Tails version are active 1.548
And Tails is running from USB drive "to_upgrade" 0.291
And the boot device has safe access rights 2.925
And the expected persistent files created with the old Tails version are present in the filesystem 1.333
And all persistent directories from the old Tails version have safe access rights 2.661
After features/support/hooks.rb:315 0.805
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
7:10.883
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 29.426
And no SquashFS delta is installed 0.181
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.342
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.087
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.283
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.473
When the network is plugged 0.035
And Tor is ready 22.767
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.819
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.436
Given I shutdown Tails and wait for the computer to power off 8.968
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.447
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.212
And the file system changes introduced in version 6.2~testoverlayfs are present 0.339
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.362
# 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.033
And Tor is ready 20.501
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.874
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.033
Given I shutdown Tails and wait for the computer to power off 4.378
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.525
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.368
And the file system changes introduced in version 6.3~testoverlayfs are present 0.500
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.332
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.283
When the network is plugged 0.048
And Tor is ready 18.429
Then the Upgrader considers the system as up-to-date 0.305
# 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.705
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.957
After features/support/hooks.rb:315 0.774
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
33.643
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.175
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.258
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 1.049
But a current signing key is available on our website 0.000
When the network is plugged 0.077
And Tor is ready 16.414
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.610
After features/support/hooks.rb:315 0.677
After features/support/hooks.rb:100 0.000