Project Number Date
test_Tails_ISO_devel 3195 15 Dec 2023, 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 15:19.989 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.353
Before features/support/hooks.rb:245 0.006
Given a computer 0.188
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.045
And I write an old version of the Tails USB image to disk "old" 19.946
When I start Tails from USB drive "old" with network unplugged 58.394
Then the boot device has safe access rights 2.829
And Tails is running from USB drive "old" 0.300
And there is no persistence partition on USB drive "old" 0.077
And process "udev-watchdog" is running 0.054
And udev-watchdog is monitoring the correct device 0.293
And I unplug USB drive "old" 0.173
After features/support/hooks.rb:291 6.586
After features/support/hooks.rb:75 0.009
Tags: @product
1:51.056
Before features/support/hooks.rb:245 0.006
Given a computer 0.209
And I start Tails from USB drive "old" with network unplugged and I login 59.695
Then Tails is running from USB drive "old" 0.441
And I create a persistent partition 41.564
And I take note of which tps features are available 1.281
Then a Tails persistence partition exists on USB drive "old" 0.786
And I shutdown Tails and wait for the computer to power off 7.078
After features/support/hooks.rb:291 0.168
After features/support/hooks.rb:75 0.010
Tags: @product
2:6.490
Before features/support/hooks.rb:245 0.006
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:40.397
Then Tails is running from USB drive "old" 0.379
And all tps features are active 2.006
When I write some files expected to persist 1.847
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.249
And all persistence configuration files have safe access rights 0.617
And all persistent directories from the old Tails version have safe access rights 2.710
And I take note of which tps features are available 0.506
And I shutdown Tails and wait for the computer to power off 3.097
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.487
After features/support/hooks.rb:291 0.094
After features/support/hooks.rb:75 0.010
Tags: @product
2:28.252
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.431
And I log in to a new session 14.645
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.074
And I plug USB drive "to_upgrade" 2.453
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:47.776
Then the running Tails is installed on USB drive "to_upgrade" 12.492
And I unplug USB drive "to_upgrade" 0.197
And I unplug USB drive "__internal" 0.182
After features/support/hooks.rb:291 3.632
After features/support/hooks.rb:75 0.000
Tags: @product
1:46.673
Before features/support/hooks.rb:245 0.006
Given a computer 0.173
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:37.154
Then all tps features from the old Tails version are active 1.636
And Tails is running from USB drive "to_upgrade" 0.307
And the boot device has safe access rights 3.363
And the expected persistent files created with the old Tails version are present in the filesystem 1.471
And all persistent directories from the old Tails version have safe access rights 2.568
After features/support/hooks.rb:291 0.616
After features/support/hooks.rb:75 0.009
Tags: @product @automatic_upgrade
5:20.601
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 10.049
And no SquashFS delta is installed 0.091
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.295
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.060
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.509
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.524
When the network is plugged 0.035
And Tor is ready 16.651
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.558
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.284
Given I shutdown Tails and wait for the computer to power off 5.154
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:39.316
Then Tails is running version 2.2~testoverlayfsng 0.094
And all tps features are active 2.278
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.403
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.260
# 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.289
When the network is plugged 0.038
And Tor is ready 14.166
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.555
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.473
Given I shutdown Tails and wait for the computer to power off 3.114
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:42.485
Then Tails is running version 2.3~testoverlayfsng 0.098
And all tps features are active 1.941
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.551
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.070
# 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.244
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.301
When the network is plugged 0.034
And Tor is ready 15.118
Then the Upgrader considers the system as up-to-date 0.255
# 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.869
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.358
After features/support/hooks.rb:291 0.758
After features/support/hooks.rb:75 0.055
Tags: @product @automatic_upgrade
23.560
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 8.923
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.352
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.065
And the signing key used by the Upgrader is outdated 0.500
But a current signing key is available on our website 0.000
When the network is plugged 0.046
And Tor is ready 12.085
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.584
After features/support/hooks.rb:291 0.681
After features/support/hooks.rb:75 0.000