Project Number Date
test_Tails_ISO_devel 3229 10 Jan 2024, 18:08

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:22.074 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:28.375
Before features/support/hooks.rb:245 0.009
Given a computer 0.238
And I create a 7200 MiB disk named "old" 0.059
And I plug USB drive "old" 1.060
And I write an old version of the Tails USB image to disk "old" 20.293
When I start Tails from USB drive "old" with network unplugged 1:2.303
Then the boot device has safe access rights 3.406
And Tails is running from USB drive "old" 0.384
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.071
And udev-watchdog is monitoring the correct device 0.286
And I unplug USB drive "old" 0.204
After features/support/hooks.rb:291 3.672
After features/support/hooks.rb:75 0.013
Tags: @product
2:0.997
Before features/support/hooks.rb:245 0.008
Given a computer 0.220
And I start Tails from USB drive "old" with network unplugged and I login 1:5.931
Then Tails is running from USB drive "old" 0.361
And I create a persistent partition 43.983
And I take note of which tps features are available 1.466
Then a Tails persistence partition exists on USB drive "old" 0.907
And I shutdown Tails and wait for the computer to power off 8.127
After features/support/hooks.rb:291 0.168
After features/support/hooks.rb:75 0.012
Tags: @product
2:32.677
Before features/support/hooks.rb:245 0.008
Given a computer 0.219
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:4.437
Then Tails is running from USB drive "old" 0.438
And all tps features are active 2.384
When I write some files expected to persist 2.274
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.269
And all persistence configuration files have safe access rights 0.677
And all persistent directories from the old Tails version have safe access rights 2.878
And I take note of which tps features are available 0.478
And I shutdown Tails and wait for the computer to power off 3.070
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.546
After features/support/hooks.rb:291 0.172
After features/support/hooks.rb:75 0.010
Tags: @product
2:36.658
Before features/support/hooks.rb:245 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.140
And I log in to a new session 18.839
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.351
And I plug USB drive "to_upgrade" 2.510
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:51.517
Then the running Tails is installed on USB drive "to_upgrade" 12.912
And I unplug USB drive "to_upgrade" 0.211
And I unplug USB drive "__internal" 0.174
After features/support/hooks.rb:291 3.629
After features/support/hooks.rb:75 0.000
Tags: @product
2:4.076
Before features/support/hooks.rb:245 0.006
Given a computer 0.205
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:52.394
Then all tps features from the old Tails version are active 1.787
And Tails is running from USB drive "to_upgrade" 0.431
And the boot device has safe access rights 3.967
And the expected persistent files created with the old Tails version are present in the filesystem 2.201
And all persistent directories from the old Tails version have safe access rights 3.088
After features/support/hooks.rb:291 0.694
After features/support/hooks.rb:75 0.024
Tags: @product @automatic_upgrade
6:9.333
Before features/support/hooks.rb:245 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.103
And no SquashFS delta is installed 0.130
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.297
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.074
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.528
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.565
When the network is plugged 0.089
And Tor is ready 18.959
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.661
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.116
Given I shutdown Tails and wait for the computer to power off 6.408
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.076
Then Tails is running version 2.2~testoverlayfsng 0.118
And all tps features are active 2.377
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.389
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.082
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.289
# 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.310
When the network is plugged 0.042
And Tor is ready 15.698
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.673
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 9.578
Given I shutdown Tails and wait for the computer to power off 4.363
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:48.824
Then Tails is running version 2.3~testoverlayfsng 0.155
And all tps features are active 2.568
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.759
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.077
# 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.375
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.361
When the network is plugged 0.048
And Tor is ready 16.499
Then the Upgrader considers the system as up-to-date 10.716
# 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 26.981
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 2.027
After features/support/hooks.rb:291 0.808
After features/support/hooks.rb:75 0.022
Tags: @product @automatic_upgrade
29.955
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.312
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.457
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.087
And the signing key used by the Upgrader is outdated 0.697
But a current signing key is available on our website 0.000
When the network is plugged 0.043
And Tor is ready 15.609
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.747
After features/support/hooks.rb:291 1.298
After features/support/hooks.rb:75 0.000