Project Number Date
test_Tails_ISO_devel 3227 09 Jan 2024, 12:27

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:17.030 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:24.546
Before features/support/hooks.rb:245 0.008
Given a computer 0.191
And I create a 7200 MiB disk named "old" 0.056
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 19.464
When I start Tails from USB drive "old" with network unplugged 59.989
Then the boot device has safe access rights 2.900
And Tails is running from USB drive "old" 0.304
And there is no persistence partition on USB drive "old" 0.088
And process "udev-watchdog" is running 0.048
And udev-watchdog is monitoring the correct device 0.263
And I unplug USB drive "old" 0.182
After features/support/hooks.rb:291 3.688
After features/support/hooks.rb:75 0.012
Tags: @product
1:58.015
Before features/support/hooks.rb:245 0.008
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login 1:4.521
Then Tails is running from USB drive "old" 0.448
And I create a persistent partition 43.401
And I take note of which tps features are available 1.495
Then a Tails persistence partition exists on USB drive "old" 0.876
And I shutdown Tails and wait for the computer to power off 7.069
After features/support/hooks.rb:291 0.158
After features/support/hooks.rb:75 0.012
Tags: @product
2:11.213
Before features/support/hooks.rb:245 0.008
Given a computer 0.280
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:45.344
Then Tails is running from USB drive "old" 0.286
And all tps features are active 2.083
When I write some files expected to persist 1.638
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.253
And all persistence configuration files have safe access rights 0.554
And all persistent directories from the old Tails version have safe access rights 2.578
And I take note of which tps features are available 0.583
And I shutdown Tails and wait for the computer to power off 3.078
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.532
After features/support/hooks.rb:291 0.119
After features/support/hooks.rb:75 0.011
Tags: @product
2:29.138
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.327
And I log in to a new session 15.129
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.263
And I plug USB drive "to_upgrade" 2.518
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:46.569
Then the running Tails is installed on USB drive "to_upgrade" 12.904
And I unplug USB drive "to_upgrade" 0.256
And I unplug USB drive "__internal" 0.169
After features/support/hooks.rb:291 6.771
After features/support/hooks.rb:75 0.000
Tags: @product
2:5.955
Before features/support/hooks.rb:245 0.009
Given a computer 0.201
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:54.653
Then all tps features from the old Tails version are active 2.842
And Tails is running from USB drive "to_upgrade" 0.366
And the boot device has safe access rights 3.580
And the expected persistent files created with the old Tails version are present in the filesystem 1.548
And all persistent directories from the old Tails version have safe access rights 2.761
After features/support/hooks.rb:291 0.602
After features/support/hooks.rb:75 0.012
Tags: @product @automatic_upgrade
5:41.230
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 10.330
And no SquashFS delta is installed 0.107
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.281
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.067
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.359
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.518
When the network is plugged 0.036
And Tor is ready 18.615
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.667
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.784
Given I shutdown Tails and wait for the computer to power off 6.387
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:48.406
Then Tails is running version 2.2~testoverlayfsng 0.102
And all tps features are active 2.123
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.359
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.084
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.278
# 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.329
When the network is plugged 0.033
And Tor is ready 16.188
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 0.577
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.514
Given I shutdown Tails and wait for the computer to power off 4.146
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:46.254
Then Tails is running version 2.3~testoverlayfsng 0.115
And all tps features are active 2.131
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.619
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.074
# 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.302
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.302
When the network is plugged 0.050
And Tor is ready 14.590
Then the Upgrader considers the system as up-to-date 0.255
# 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.651
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.584
After features/support/hooks.rb:291 0.769
After features/support/hooks.rb:75 0.028
Tags: @product @automatic_upgrade
26.930
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 9.639
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.326
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.058
And the signing key used by the Upgrader is outdated 0.961
But a current signing key is available on our website 0.000
When the network is plugged 0.047
And Tor is ready 13.275
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.621
After features/support/hooks.rb:291 0.688
After features/support/hooks.rb:75 0.000