Project Number Date
test_Tails_ISO_devel 3243 19 Jan 2024, 13:28

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:38.571 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:35.158
Before features/support/hooks.rb:245 0.009
Given a computer 0.261
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.075
And I write an old version of the Tails USB image to disk "old" 20.285
When I start Tails from USB drive "old" with network unplugged 1:9.047
Then the boot device has safe access rights 3.389
And Tails is running from USB drive "old" 0.383
And there is no persistence partition on USB drive "old" 0.077
And process "udev-watchdog" is running 0.061
And udev-watchdog is monitoring the correct device 0.309
And I unplug USB drive "old" 0.215
After features/support/hooks.rb:291 3.513
After features/support/hooks.rb:75 0.013
Tags: @product
2:3.878
Before features/support/hooks.rb:245 0.019
Given a computer 0.233
And I start Tails from USB drive "old" with network unplugged and I login 1:6.899
Then Tails is running from USB drive "old" 0.377
And I create a persistent partition 45.642
And I take note of which tps features are available 1.738
Then a Tails persistence partition exists on USB drive "old" 0.892
And I shutdown Tails and wait for the computer to power off 8.094
After features/support/hooks.rb:291 0.164
After features/support/hooks.rb:75 0.012
Tags: @product
2:27.711
Before features/support/hooks.rb:245 0.006
Given a computer 0.212
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:58.841
Then Tails is running from USB drive "old" 0.368
And all tps features are active 2.105
When I write some files expected to persist 1.777
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.283
And all persistence configuration files have safe access rights 0.537
And all persistent directories from the old Tails version have safe access rights 2.960
And I take note of which tps features are available 0.511
And I shutdown Tails and wait for the computer to power off 3.073
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.038
After features/support/hooks.rb:291 0.165
After features/support/hooks.rb:75 0.011
Tags: @product
2:34.948
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.236
And I log in to a new session 18.065
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.441
And I plug USB drive "to_upgrade" 2.498
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:46.812
Then the running Tails is installed on USB drive "to_upgrade" 14.494
And I unplug USB drive "to_upgrade" 0.203
And I unplug USB drive "__internal" 0.196
After features/support/hooks.rb:291 6.745
After features/support/hooks.rb:75 0.000
Tags: @product
2:4.907
Before features/support/hooks.rb:245 0.009
Given a computer 0.242
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:53.453
Then all tps features from the old Tails version are active 1.906
And Tails is running from USB drive "to_upgrade" 0.377
And the boot device has safe access rights 4.015
And the expected persistent files created with the old Tails version are present in the filesystem 1.739
And all persistent directories from the old Tails version have safe access rights 3.173
After features/support/hooks.rb:291 0.741
After features/support/hooks.rb:75 0.011
Tags: @product @automatic_upgrade
6:22.778
Before features/support/hooks.rb:245 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.897
And no SquashFS delta is installed 0.100
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.340
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.050
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.407
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.671
When the network is plugged 0.032
And Tor is ready 47.130
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 0.613
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.259
Given I shutdown Tails and wait for the computer to power off 6.074
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.810
Then Tails is running version 2.2~testoverlayfsng 0.143
And all tps features are active 2.442
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.461
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.088
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.350
# 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.403
When the network is plugged 0.041
And Tor is ready 17.165
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.721
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.629
Given I shutdown Tails and wait for the computer to power off 4.200
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.675
Then Tails is running version 2.3~testoverlayfsng 0.149
And all tps features are active 2.157
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.652
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.081
# 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.351
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.392
When the network is plugged 0.035
And Tor is ready 17.993
Then the Upgrader considers the system as up-to-date 0.314
# 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.554
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.378
After features/support/hooks.rb:291 0.778
After features/support/hooks.rb:75 0.021
Tags: @product @automatic_upgrade
29.189
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.297
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.094
And the signing key used by the Upgrader is outdated 0.626
But a current signing key is available on our website 0.000
When the network is plugged 0.044
And Tor is ready 14.991
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.856
After features/support/hooks.rb:291 0.819
After features/support/hooks.rb:75 0.000