Project Number Date
test_Tails_ISO_devel 3415 04 Jun 2024, 18:47

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:26.110 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:5.795
Before features/support/hooks.rb:269 0.007
Given a computer 0.268
And I create a 7200 MiB disk named "old" 0.061
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 30.980
When I start Tails from USB drive "old" with network unplugged 1:29.385
Then the boot device has safe access rights 2.940
And Tails is running from USB drive "old" 0.333
And there is no persistence partition on USB drive "old" 0.082
And process "udev-watchdog" is running 0.110
And udev-watchdog is monitoring the correct device 0.361
And I unplug USB drive "old" 0.218
After features/support/hooks.rb:315 9.083
After features/support/hooks.rb:100 0.010
Tags: @product
2:17.904
Before features/support/hooks.rb:269 0.007
Given a computer 0.236
And I start Tails from USB drive "old" with network unplugged and I login 1:27.850
Then Tails is running from USB drive "old" 0.336
And I create a persistent partition 36.940
And I take note of which tps features are available 1.464
Then a Tails persistence partition exists on USB drive "old" 0.798
And I shutdown Tails and wait for the computer to power off 10.277
After features/support/hooks.rb:315 0.142
After features/support/hooks.rb:100 0.010
Tags: @product
3:2.054
Before features/support/hooks.rb:269 0.005
Given a computer 0.220
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:24.948
Then Tails is running from USB drive "old" 0.447
And all tps features are active 2.194
When I write some files expected to persist 1.793
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.247
And all persistence configuration files have safe access rights 0.376
And all persistent directories from the old Tails version have safe access rights 2.686
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.432
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.211
After features/support/hooks.rb:315 0.145
After features/support/hooks.rb:100 0.012
Tags: @product
2:30.807
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 10.943
And I log in to a new session 21.857
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.680
And I plug USB drive "to_upgrade" 2.477
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.680
Then the running Tails is installed on USB drive "to_upgrade" 19.696
And I unplug USB drive "to_upgrade" 0.255
And I unplug USB drive "__internal" 0.214
After features/support/hooks.rb:315 2.041
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.885
Before features/support/hooks.rb:269 0.008
Given a computer 0.225
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.855
Then all tps features from the old Tails version are active 1.602
And Tails is running from USB drive "to_upgrade" 0.351
And the boot device has safe access rights 3.791
And the expected persistent files created with the old Tails version are present in the filesystem 1.500
And all persistent directories from the old Tails version have safe access rights 2.558
After features/support/hooks.rb:315 0.909
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:37.181
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 18.966
And no SquashFS delta is installed 0.140
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.458
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.357
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.526
When the network is plugged 0.097
And Tor is ready 20.708
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.321
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.796
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 2:7.143
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.204
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.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.334
# 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.282
When the network is plugged 0.044
And Tor is ready 18.076
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.779
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.984
Given I shutdown Tails and wait for the computer to power off 4.144
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.477
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.032
And the file system changes introduced in version 6.3~testoverlayfs are present 0.489
And only the 6.3~testoverlayfs SquashFS delta is installed 0.068
# 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.342
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.323
When the network is plugged 0.035
And Tor is ready 18.054
Then the Upgrader considers the system as up-to-date 0.329
# 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 14.458
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.907
After features/support/hooks.rb:315 0.715
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
38.482
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.325
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.515
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 1.556
But a current signing key is available on our website 0.000
When the network is plugged 0.036
And Tor is ready 19.185
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.812
After features/support/hooks.rb:315 0.662
After features/support/hooks.rb:100 0.000