Project Number Date
test_Tails_ISO_stable 4675 20 Feb 2024, 12:19

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 17:10.607 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:30.490
Before features/support/hooks.rb:245 0.007
Given a computer 0.210
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 22.578
When I start Tails from USB drive "old" with network unplugged 1:2.258
Then the boot device has safe access rights 3.449
And Tails is running from USB drive "old" 0.338
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.063
And udev-watchdog is monitoring the correct device 0.252
And I unplug USB drive "old" 0.175
After features/support/hooks.rb:291 3.464
After features/support/hooks.rb:75 0.012
Tags: @product
1:58.934
Before features/support/hooks.rb:245 0.006
Given a computer 0.205
And I start Tails from USB drive "old" with network unplugged and I login 1:4.930
Then Tails is running from USB drive "old" 0.436
And I create a persistent partition 43.957
And I take note of which tps features are available 1.425
Then a Tails persistence partition exists on USB drive "old" 0.923
And I shutdown Tails and wait for the computer to power off 7.056
After features/support/hooks.rb:291 0.172
After features/support/hooks.rb:75 0.013
Tags: @product
2:17.542
Before features/support/hooks.rb:245 0.005
Given a computer 0.219
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:51.115
Then Tails is running from USB drive "old" 0.356
And all tps features are active 2.235
When I write some files expected to persist 1.740
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.218
And all persistence configuration files have safe access rights 0.427
And all persistent directories from the old Tails version have safe access rights 2.717
And I take note of which tps features are available 0.566
And I shutdown Tails and wait for the computer to power off 3.066
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.878
After features/support/hooks.rb:291 0.126
After features/support/hooks.rb:75 0.008
Tags: @product
2:36.551
Before features/support/hooks.rb:245 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 9.776
And I log in to a new session 20.633
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.875
And I plug USB drive "to_upgrade" 2.542
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:47.398
Then the running Tails is installed on USB drive "to_upgrade" 13.913
And I unplug USB drive "to_upgrade" 0.208
And I unplug USB drive "__internal" 0.202
After features/support/hooks.rb:291 6.698
After features/support/hooks.rb:75 0.000
Tags: @product
2:5.797
Before features/support/hooks.rb:245 0.007
Given a computer 0.244
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:54.840
Then all tps features from the old Tails version are active 1.796
And Tails is running from USB drive "to_upgrade" 0.379
And the boot device has safe access rights 3.883
And the expected persistent files created with the old Tails version are present in the filesystem 1.779
And all persistent directories from the old Tails version have safe access rights 2.873
After features/support/hooks.rb:291 0.765
After features/support/hooks.rb:75 0.024
Tags: @product @automatic_upgrade
6:11.045
Before features/support/hooks.rb:245 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.751
And no SquashFS delta is installed 0.151
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.422
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.091
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.358
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.566
When the network is plugged 0.041
And Tor is ready 18.143
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.779
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.354
Given I shutdown Tails and wait for the computer to power off 8.314
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.962
Then Tails is running version 2.2~testoverlayfsng 0.124
And all tps features are active 2.141
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.373
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.310
# We'll really install Tails_amd64_2.0~testoverlayfsng_to_2.3~testoverlayfsng.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 2.1~testoverlayfsng was initially installed 0.286
When the network is plugged 0.047
And Tor is ready 15.162
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.770
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.897
Given I shutdown Tails and wait for the computer to power off 4.494
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:48.134
Then Tails is running version 2.3~testoverlayfsng 0.100
And all tps features are active 2.098
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.671
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.091
# 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.383
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.324
When the network is plugged 0.043
And Tor is ready 17.320
Then the Upgrader considers the system as up-to-date 0.296
# 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 25.465
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.494
After features/support/hooks.rb:291 1.195
After features/support/hooks.rb:75 0.022
Tags: @product @automatic_upgrade
30.244
Before features/support/hooks.rb:245 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.177
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.439
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.075
And the signing key used by the Upgrader is outdated 0.584
But a current signing key is available on our website 0.000
When the network is plugged 0.043
And Tor is ready 15.183
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.740
After features/support/hooks.rb:291 0.772
After features/support/hooks.rb:75 0.000