Project Number Date
test_Tails_ISO_stable 4642 28 Jan 2024, 12:17

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:0.972 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:23.224
Before features/support/hooks.rb:245 0.005
Given a computer 0.125
And I create a 7200 MiB disk named "old" 0.026
And I plug USB drive "old" 1.040
And I write an old version of the Tails USB image to disk "old" 18.783
When I start Tails from USB drive "old" with network unplugged 59.493
Then the boot device has safe access rights 2.868
And Tails is running from USB drive "old" 0.302
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.070
And udev-watchdog is monitoring the correct device 0.260
And I unplug USB drive "old" 0.190
After features/support/hooks.rb:291 3.506
After features/support/hooks.rb:75 0.009
Tags: @product
1:55.283
Before features/support/hooks.rb:245 0.006
Given a computer 0.134
And I start Tails from USB drive "old" with network unplugged and I login 1:1.650
Then Tails is running from USB drive "old" 0.439
And I create a persistent partition 44.021
And I take note of which tps features are available 1.195
Then a Tails persistence partition exists on USB drive "old" 0.777
And I shutdown Tails and wait for the computer to power off 7.064
After features/support/hooks.rb:291 0.121
After features/support/hooks.rb:75 0.009
Tags: @product
2:17.802
Before features/support/hooks.rb:245 0.006
Given a computer 0.134
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:52.978
Then Tails is running from USB drive "old" 0.344
And all tps features are active 1.680
When I write some files expected to persist 1.702
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.226
And all persistence configuration files have safe access rights 0.343
And all persistent directories from the old Tails version have safe access rights 2.533
And I take note of which tps features are available 0.281
And I shutdown Tails and wait for the computer to power off 3.053
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.525
After features/support/hooks.rb:291 0.128
After features/support/hooks.rb:75 0.009
Tags: @product
2:29.664
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.011
And I log in to a new session 14.408
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.112
And I plug USB drive "to_upgrade" 2.377
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:49.972
Then the running Tails is installed on USB drive "to_upgrade" 12.431
And I unplug USB drive "to_upgrade" 0.179
And I unplug USB drive "__internal" 0.170
After features/support/hooks.rb:291 2.076
After features/support/hooks.rb:75 0.000
Tags: @product
1:52.513
Before features/support/hooks.rb:245 0.006
Given a computer 0.137
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:42.930
Then all tps features from the old Tails version are active 1.296
And Tails is running from USB drive "to_upgrade" 0.363
And the boot device has safe access rights 3.375
And the expected persistent files created with the old Tails version are present in the filesystem 1.524
And all persistent directories from the old Tails version have safe access rights 2.885
After features/support/hooks.rb:291 0.684
After features/support/hooks.rb:75 0.009
Tags: @product @automatic_upgrade
6:8.847
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 10.179
And no SquashFS delta is installed 0.075
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.278
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.088
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.370
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.531
When the network is plugged 0.031
And Tor is ready 15.925
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.591
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.796
Given I shutdown Tails and wait for the computer to power off 6.318
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.913
Then Tails is running version 2.2~testoverlayfsng 0.090
And all tps features are active 1.846
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.398
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.257
# 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.281
When the network is plugged 0.030
And Tor is ready 17.640
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.523
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.225
Given I shutdown Tails and wait for the computer to power off 4.091
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:43.191
Then Tails is running version 2.3~testoverlayfsng 0.096
And all tps features are active 1.739
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.579
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.072
# 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.266
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.497
When the network is plugged 0.029
And Tor is ready 42.906
Then the Upgrader considers the system as up-to-date 0.279
# 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 28.406
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.232
After features/support/hooks.rb:291 0.790
After features/support/hooks.rb:75 0.015
Tags: @product @automatic_upgrade
53.636
Before features/support/hooks.rb:245 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.777
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.291
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.060
And the signing key used by the Upgrader is outdated 0.639
But a current signing key is available on our website 0.000
When the network is plugged 0.021
And Tor is ready 42.276
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 0.570
After features/support/hooks.rb:291 0.888
After features/support/hooks.rb:75 0.000