Project Number Date
test_Tails_ISO_devel 3256 28 Jan 2024, 12:31

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:26.643 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:33.334
Before features/support/hooks.rb:245 0.008
Given a computer 0.201
And I create a 7200 MiB disk named "old" 0.064
And I plug USB drive "old" 1.057
And I write an old version of the Tails USB image to disk "old" 22.056
When I start Tails from USB drive "old" with network unplugged 1:5.438
Then the boot device has safe access rights 3.519
And Tails is running from USB drive "old" 0.336
And there is no persistence partition on USB drive "old" 0.078
And process "udev-watchdog" is running 0.065
And udev-watchdog is monitoring the correct device 0.321
And I unplug USB drive "old" 0.194
After features/support/hooks.rb:291 3.525
After features/support/hooks.rb:75 0.013
Tags: @product
2:5.250
Before features/support/hooks.rb:245 0.008
Given a computer 0.251
And I start Tails from USB drive "old" with network unplugged and I login 1:8.396
Then Tails is running from USB drive "old" 0.362
And I create a persistent partition 45.392
And I take note of which tps features are available 1.613
Then a Tails persistence partition exists on USB drive "old" 0.998
And I shutdown Tails and wait for the computer to power off 8.235
After features/support/hooks.rb:291 0.129
After features/support/hooks.rb:75 0.010
Tags: @product
2:23.222
Before features/support/hooks.rb:245 0.009
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:52.775
Then Tails is running from USB drive "old" 0.409
And all tps features are active 2.466
When I write some files expected to persist 1.961
# 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.483
And all persistent directories from the old Tails version have safe access rights 3.024
And I take note of which tps features are available 0.591
And I shutdown Tails and wait for the computer to power off 3.077
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.018
After features/support/hooks.rb:291 0.117
After features/support/hooks.rb:75 0.012
Tags: @product
2:34.954
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 10.650
And I log in to a new session 17.245
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.492
And I plug USB drive "to_upgrade" 2.513
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:48.523
Then the running Tails is installed on USB drive "to_upgrade" 14.123
And I unplug USB drive "to_upgrade" 0.208
And I unplug USB drive "__internal" 0.196
After features/support/hooks.rb:291 7.155
After features/support/hooks.rb:75 0.000
Tags: @product
2:0.886
Before features/support/hooks.rb:245 0.008
Given a computer 0.220
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:50.109
Then all tps features from the old Tails version are active 1.685
And Tails is running from USB drive "to_upgrade" 0.375
And the boot device has safe access rights 3.702
And the expected persistent files created with the old Tails version are present in the filesystem 1.670
And all persistent directories from the old Tails version have safe access rights 3.122
After features/support/hooks.rb:291 0.819
After features/support/hooks.rb:75 0.016
Tags: @product @automatic_upgrade
6:19.361
Before features/support/hooks.rb:245 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.877
And no SquashFS delta is installed 0.104
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.446
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.403
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.666
When the network is plugged 0.053
And Tor is ready 14.773
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 3.983
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.937
Given I shutdown Tails and wait for the computer to power off 6.313
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:50.509
Then Tails is running version 2.2~testoverlayfsng 0.110
And all tps features are active 2.397
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.439
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.090
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.352
# 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.360
When the network is plugged 0.039
And Tor is ready 15.596
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.754
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 10.258
Given I shutdown Tails and wait for the computer to power off 4.336
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.335
Then Tails is running version 2.3~testoverlayfsng 0.105
And all tps features are active 2.110
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.611
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.304
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.322
When the network is plugged 0.035
And Tor is ready 43.828
Then the Upgrader considers the system as up-to-date 0.264
# 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.023
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.467
After features/support/hooks.rb:291 0.820
After features/support/hooks.rb:75 0.022
Tags: @product @automatic_upgrade
29.633
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.643
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.372
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.056
And the signing key used by the Upgrader is outdated 0.699
But a current signing key is available on our website 0.000
When the network is plugged 0.035
And Tor is ready 15.086
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.739
After features/support/hooks.rb:291 0.629
After features/support/hooks.rb:75 0.000