Project Number Date
test_Tails_ISO_devel 3223 05 Jan 2024, 12:16

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:5.104 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:29.402
Before features/support/hooks.rb:245 0.007
Given a computer 0.188
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 20.399
When I start Tails from USB drive "old" with network unplugged 1:3.606
Then the boot device has safe access rights 3.185
And Tails is running from USB drive "old" 0.324
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.059
And udev-watchdog is monitoring the correct device 0.298
And I unplug USB drive "old" 0.177
After features/support/hooks.rb:291 3.716
After features/support/hooks.rb:75 0.012
Tags: @product
1:59.198
Before features/support/hooks.rb:245 0.008
Given a computer 0.210
And I start Tails from USB drive "old" with network unplugged and I login 1:3.108
Then Tails is running from USB drive "old" 0.512
And I create a persistent partition 44.831
And I take note of which tps features are available 1.569
Then a Tails persistence partition exists on USB drive "old" 0.902
And I shutdown Tails and wait for the computer to power off 8.065
After features/support/hooks.rb:291 0.166
After features/support/hooks.rb:75 0.012
Tags: @product
2:22.566
Before features/support/hooks.rb:245 0.007
Given a computer 0.201
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:52.424
Then Tails is running from USB drive "old" 0.377
And all tps features are active 2.151
When I write some files expected to persist 2.863
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.258
And all persistence configuration files have safe access rights 0.614
And all persistent directories from the old Tails version have safe access rights 2.916
And I take note of which tps features are available 0.535
And I shutdown Tails and wait for the computer to power off 3.055
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.167
After features/support/hooks.rb:291 0.153
After features/support/hooks.rb:75 0.016
Tags: @product
2:45.829
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 11.718
And I log in to a new session 22.476
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.677
And I plug USB drive "to_upgrade" 2.535
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:51.806
Then the running Tails is installed on USB drive "to_upgrade" 15.218
And I unplug USB drive "to_upgrade" 0.203
And I unplug USB drive "__internal" 0.193
After features/support/hooks.rb:291 1.049
After features/support/hooks.rb:75 0.000
Tags: @product
1:59.073
Before features/support/hooks.rb:245 0.008
Given a computer 0.203
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:48.580
Then all tps features from the old Tails version are active 1.812
And Tails is running from USB drive "to_upgrade" 0.336
And the boot device has safe access rights 3.726
And the expected persistent files created with the old Tails version are present in the filesystem 1.544
And all persistent directories from the old Tails version have safe access rights 2.870
After features/support/hooks.rb:291 0.785
After features/support/hooks.rb:75 0.013
Tags: @product @automatic_upgrade
6:1.701
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 12.347
And no SquashFS delta is installed 0.097
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.536
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.078
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.515
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.606
When the network is plugged 0.054
And Tor is ready 20.417
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.732
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 10.856
Given I shutdown Tails and wait for the computer to power off 6.349
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.692
Then Tails is running version 2.2~testoverlayfsng 0.110
And all tps features are active 2.438
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.441
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.063
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.283
# 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.384
When the network is plugged 0.095
And Tor is ready 14.770
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.851
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.363
Given I shutdown Tails and wait for the computer to power off 4.365
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.415
Then Tails is running version 2.3~testoverlayfsng 0.103
And all tps features are active 2.290
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.624
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.073
# 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.288
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.319
When the network is plugged 0.045
And Tor is ready 14.983
Then the Upgrader considers the system as up-to-date 0.288
# 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 24.871
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.942
After features/support/hooks.rb:291 0.862
After features/support/hooks.rb:75 0.020
Tags: @product @automatic_upgrade
27.331
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 9.732
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.332
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.053
And the signing key used by the Upgrader is outdated 0.678
But a current signing key is available on our website 0.000
When the network is plugged 0.032
And Tor is ready 12.829
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 3.672
After features/support/hooks.rb:291 0.927
After features/support/hooks.rb:75 0.000