Project Number Date
test_Tails_ISO_devel 3230 10 Jan 2024, 22:38

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:8.599 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:28.034
Before features/support/hooks.rb:245 0.007
Given a computer 0.158
And I create a 7200 MiB disk named "old" 0.040
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 21.715
When I start Tails from USB drive "old" with network unplugged 1:1.256
Then the boot device has safe access rights 2.968
And Tails is running from USB drive "old" 0.294
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.059
And udev-watchdog is monitoring the correct device 0.247
And I unplug USB drive "old" 0.181
After features/support/hooks.rb:291 3.455
After features/support/hooks.rb:75 0.010
Tags: @product
1:59.395
Before features/support/hooks.rb:245 0.006
Given a computer 0.147
And I start Tails from USB drive "old" with network unplugged and I login 1:4.276
Then Tails is running from USB drive "old" 0.466
And I create a persistent partition 45.109
And I take note of which tps features are available 1.335
Then a Tails persistence partition exists on USB drive "old" 0.962
And I shutdown Tails and wait for the computer to power off 7.097
After features/support/hooks.rb:291 0.163
After features/support/hooks.rb:75 0.008
Tags: @product
2:22.970
Before features/support/hooks.rb:245 0.004
Given a computer 0.140
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:57.260
Then Tails is running from USB drive "old" 0.391
And all tps features are active 1.678
When I write some files expected to persist 1.815
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.246
And all persistence configuration files have safe access rights 0.574
And all persistent directories from the old Tails version have safe access rights 2.683
And I take note of which tps features are available 0.287
And I shutdown Tails and wait for the computer to power off 3.069
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.822
After features/support/hooks.rb:291 0.100
After features/support/hooks.rb:75 0.010
Tags: @product
2:36.102
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 12.127
And I log in to a new session 16.348
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.257
And I plug USB drive "to_upgrade" 2.476
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:51.023
Then the running Tails is installed on USB drive "to_upgrade" 12.504
And I unplug USB drive "to_upgrade" 0.187
And I unplug USB drive "__internal" 0.176
After features/support/hooks.rb:291 0.906
After features/support/hooks.rb:75 0.000
Tags: @product
1:58.591
Before features/support/hooks.rb:245 0.007
Given a computer 0.145
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:48.978
Then all tps features from the old Tails version are active 1.310
And Tails is running from USB drive "to_upgrade" 0.301
And the boot device has safe access rights 3.416
And the expected persistent files created with the old Tails version are present in the filesystem 1.507
And all persistent directories from the old Tails version have safe access rights 2.930
After features/support/hooks.rb:291 0.709
After features/support/hooks.rb:75 0.008
Tags: @product @automatic_upgrade
6:14.727
Before features/support/hooks.rb:245 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.458
And no SquashFS delta is installed 0.110
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.400
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.137
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.366
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.603
When the network is plugged 0.030
And Tor is ready 17.621
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.728
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.934
Given I shutdown Tails and wait for the computer to power off 5.293
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.701
Then Tails is running version 2.2~testoverlayfsng 0.109
And all tps features are active 1.913
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.381
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.081
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.273
# 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.315
When the network is plugged 0.048
And Tor is ready 44.193
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 0.560
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.957
Given I shutdown Tails and wait for the computer to power off 4.138
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:45.207
Then Tails is running version 2.3~testoverlayfsng 0.137
And all tps features are active 1.810
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.763
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.103
# 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.337
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.288
When the network is plugged 0.028
And Tor is ready 16.149
Then the Upgrader considers the system as up-to-date 0.252
# 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.534
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.753
After features/support/hooks.rb:291 0.767
After features/support/hooks.rb:75 0.020
Tags: @product @automatic_upgrade
28.779
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.530
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.499
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.066
And the signing key used by the Upgrader is outdated 0.483
But a current signing key is available on our website 0.000
When the network is plugged 0.023
And Tor is ready 15.442
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.733
After features/support/hooks.rb:291 1.293
After features/support/hooks.rb:75 0.000