Project Number Date
test_Tails_ISO_devel 3425 13 Jun 2024, 13:14

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 20:21.695 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:20.302
Before features/support/hooks.rb:269 0.008
Given a computer 0.239
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 28.819
When I start Tails from USB drive "old" with network unplugged 1:46.125
Then the boot device has safe access rights 3.016
And Tails is running from USB drive "old" 0.336
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.104
And udev-watchdog is monitoring the correct device 0.289
And I unplug USB drive "old" 0.208
After features/support/hooks.rb:315 6.984
After features/support/hooks.rb:100 0.012
Tags: @product
2:12.859
Before features/support/hooks.rb:269 0.007
Given a computer 0.216
And I start Tails from USB drive "old" with network unplugged and I login 1:23.912
Then Tails is running from USB drive "old" 0.393
And I create a persistent partition 37.076
And I take note of which tps features are available 1.579
Then a Tails persistence partition exists on USB drive "old" 0.941
And I shutdown Tails and wait for the computer to power off 8.738
After features/support/hooks.rb:315 0.287
After features/support/hooks.rb:100 0.013
Tags: @product
3:3.154
Before features/support/hooks.rb:269 0.008
Given a computer 0.242
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:25.935
Then Tails is running from USB drive "old" 0.348
And all tps features are active 2.185
When I write some files expected to persist 1.668
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.219
And all persistence configuration files have safe access rights 0.363
And all persistent directories from the old Tails version have safe access rights 2.426
And I take note of which tps features are available 0.477
And I shutdown Tails and wait for the computer to power off 4.437
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.847
After features/support/hooks.rb:315 0.133
After features/support/hooks.rb:100 0.011
Tags: @product
2:38.591
Before features/support/hooks.rb:269 0.020
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.195
And I log in to a new session 23.068
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.673
And I plug USB drive "to_upgrade" 2.556
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.937
Then the running Tails is installed on USB drive "to_upgrade" 21.570
And I unplug USB drive "to_upgrade" 0.244
And I unplug USB drive "__internal" 0.343
After features/support/hooks.rb:315 2.091
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.740
Before features/support/hooks.rb:269 0.007
Given a computer 0.260
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.085
Then all tps features from the old Tails version are active 1.681
And Tails is running from USB drive "to_upgrade" 0.332
And the boot device has safe access rights 3.262
And the expected persistent files created with the old Tails version are present in the filesystem 1.659
And all persistent directories from the old Tails version have safe access rights 2.459
After features/support/hooks.rb:315 0.642
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
7:10.537
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 12.598
And no SquashFS delta is installed 0.132
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.430
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.351
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.532
When the network is plugged 0.036
And Tor is ready 48.865
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.583
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.549
Given I shutdown Tails and wait for the computer to power off 9.295
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:17.549
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.254
And the file system changes introduced in version 6.2~testoverlayfs are present 0.319
And only the 6.2~testoverlayfs SquashFS delta is installed 0.107
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.400
# 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.380
When the network is plugged 0.047
And Tor is ready 17.557
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.966
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.899
Given I shutdown Tails and wait for the computer to power off 6.632
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.929
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 3.165
And the file system changes introduced in version 6.3~testoverlayfs are present 0.484
And only the 6.3~testoverlayfs SquashFS delta is installed 0.064
# 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.431
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.287
When the network is plugged 0.035
And Tor is ready 21.942
Then the Upgrader considers the system as up-to-date 0.347
# 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 15.099
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.153
After features/support/hooks.rb:315 1.443
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
40.509
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 13.329
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.346
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 1.348
But a current signing key is available on our website 0.000
When the network is plugged 0.037
And Tor is ready 18.736
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.657
After features/support/hooks.rb:315 1.468
After features/support/hooks.rb:100 0.000