Project Number Date
test_Tails_ISO_devel 3253 25 Jan 2024, 22:07

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 16:33.841 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:26.852
Before features/support/hooks.rb:245 0.005
Given a computer 0.146
And I create a 7200 MiB disk named "old" 0.027
And I plug USB drive "old" 1.041
And I write an old version of the Tails USB image to disk "old" 18.839
When I start Tails from USB drive "old" with network unplugged 1:2.944
Then the boot device has safe access rights 2.958
And Tails is running from USB drive "old" 0.314
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.055
And udev-watchdog is monitoring the correct device 0.282
And I unplug USB drive "old" 0.178
After features/support/hooks.rb:291 3.507
After features/support/hooks.rb:75 0.012
Tags: @product
2:0.172
Before features/support/hooks.rb:245 0.007
Given a computer 0.161
And I start Tails from USB drive "old" with network unplugged and I login 1:5.369
Then Tails is running from USB drive "old" 0.400
And I create a persistent partition 43.872
And I take note of which tps features are available 1.409
Then a Tails persistence partition exists on USB drive "old" 0.884
And I shutdown Tails and wait for the computer to power off 8.073
After features/support/hooks.rb:291 0.099
After features/support/hooks.rb:75 0.011
Tags: @product
2:14.847
Before features/support/hooks.rb:245 0.009
Given a computer 0.316
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:48.874
Then Tails is running from USB drive "old" 0.356
And all tps features are active 1.654
When I write some files expected to persist 1.814
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.233
And all persistence configuration files have safe access rights 0.429
And all persistent directories from the old Tails version have safe access rights 2.557
And I take note of which tps features are available 0.357
And I shutdown Tails and wait for the computer to power off 3.061
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.192
After features/support/hooks.rb:291 0.154
After features/support/hooks.rb:75 0.010
Tags: @product
2:32.867
Before features/support/hooks.rb:245 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.170
And I log in to a new session 17.736
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.558
And I plug USB drive "to_upgrade" 2.494
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:47.882
Then the running Tails is installed on USB drive "to_upgrade" 12.650
And I unplug USB drive "to_upgrade" 0.187
And I unplug USB drive "__internal" 0.187
After features/support/hooks.rb:291 2.134
After features/support/hooks.rb:75 0.000
Tags: @product
1:59.157
Before features/support/hooks.rb:245 0.007
Given a computer 0.205
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:48.856
Then all tps features from the old Tails version are active 1.564
And Tails is running from USB drive "to_upgrade" 0.366
And the boot device has safe access rights 3.573
And the expected persistent files created with the old Tails version are present in the filesystem 1.594
And all persistent directories from the old Tails version have safe access rights 2.995
After features/support/hooks.rb:291 0.671
After features/support/hooks.rb:75 0.010
Tags: @product @automatic_upgrade
5:54.369
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.767
And no SquashFS delta is installed 0.094
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.266
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.115
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.425
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.492
When the network is plugged 0.025
And Tor is ready 15.526
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 3.707
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.553
Given I shutdown Tails and wait for the computer to power off 7.386
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:50.661
Then Tails is running version 2.2~testoverlayfsng 0.131
And all tps features are active 2.019
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.366
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.051
# 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.307
When the network is plugged 0.030
And Tor is ready 15.496
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.783
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.664
Given I shutdown Tails and wait for the computer to power off 4.272
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.762
Then Tails is running version 2.3~testoverlayfsng 0.125
And all tps features are active 2.052
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.664
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.092
# 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.289
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.301
When the network is plugged 0.043
And Tor is ready 15.397
Then the Upgrader considers the system as up-to-date 0.342
# 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 29.149
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.692
After features/support/hooks.rb:291 0.754
After features/support/hooks.rb:75 0.023
Tags: @product @automatic_upgrade
25.573
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.989
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.350
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.068
And the signing key used by the Upgrader is outdated 1.123
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 13.432
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.590
After features/support/hooks.rb:291 0.670
After features/support/hooks.rb:75 0.000