Project Number Date
test_Tails_ISO_stable 4597 31 Dec 2023, 12:06

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 16:52.466 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:45.145
Before features/support/hooks.rb:245 0.005
Given a computer 0.161
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 18.626
When I start Tails from USB drive "old" with network unplugged 1:21.403
Then the boot device has safe access rights 2.980
And Tails is running from USB drive "old" 0.308
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.279
And I unplug USB drive "old" 0.186
After features/support/hooks.rb:291 3.465
After features/support/hooks.rb:75 0.009
Tags: @product
1:58.888
Before features/support/hooks.rb:245 0.006
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login 1:4.900
Then Tails is running from USB drive "old" 0.503
And I create a persistent partition 42.805
And I take note of which tps features are available 1.581
Then a Tails persistence partition exists on USB drive "old" 0.820
And I shutdown Tails and wait for the computer to power off 8.088
After features/support/hooks.rb:291 0.123
After features/support/hooks.rb:75 0.008
Tags: @product
2:14.358
Before features/support/hooks.rb:245 0.004
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:47.805
Then Tails is running from USB drive "old" 0.335
And all tps features are active 2.176
When I write some files expected to persist 1.964
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.227
And all persistence configuration files have safe access rights 0.616
And all persistent directories from the old Tails version have safe access rights 2.545
And I take note of which tps features are available 0.581
And I shutdown Tails and wait for the computer to power off 3.056
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.854
After features/support/hooks.rb:291 0.105
After features/support/hooks.rb:75 0.010
Tags: @product
2:31.965
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 9.561
And I log in to a new session 15.349
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.165
And I plug USB drive "to_upgrade" 2.585
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:50.222
Then the running Tails is installed on USB drive "to_upgrade" 12.658
And I unplug USB drive "to_upgrade" 0.248
And I unplug USB drive "__internal" 0.173
After features/support/hooks.rb:291 6.625
After features/support/hooks.rb:75 0.000
Tags: @product
2:1.364
Before features/support/hooks.rb:245 0.004
Given a computer 0.171
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:51.175
Then all tps features from the old Tails version are active 1.904
And Tails is running from USB drive "to_upgrade" 0.348
And the boot device has safe access rights 3.646
And the expected persistent files created with the old Tails version are present in the filesystem 1.497
And all persistent directories from the old Tails version have safe access rights 2.620
After features/support/hooks.rb:291 0.663
After features/support/hooks.rb:75 0.007
Tags: @product @automatic_upgrade
5:55.447
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 11.415
And no SquashFS delta is installed 0.100
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.360
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.087
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.362
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.628
When the network is plugged 0.045
And Tor is ready 21.036
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.615
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 7.934
Given I shutdown Tails and wait for the computer to power off 6.243
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.761
Then Tails is running version 2.2~testoverlayfsng 0.115
And all tps features are active 2.416
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.353
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.323
# 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.290
When the network is plugged 0.033
And Tor is ready 17.027
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.664
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.205
Given I shutdown Tails and wait for the computer to power off 4.279
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:42.891
Then Tails is running version 2.3~testoverlayfsng 0.127
And all tps features are active 1.939
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.569
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.067
# 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.269
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.426
When the network is plugged 0.048
And Tor is ready 17.043
Then the Upgrader considers the system as up-to-date 0.248
# 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.326
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.122
After features/support/hooks.rb:291 0.736
After features/support/hooks.rb:75 0.035
Tags: @product @automatic_upgrade
25.296
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 9.346
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.337
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 1.255
But a current signing key is available on our website 0.000
When the network is plugged 0.053
And Tor is ready 11.578
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.657
After features/support/hooks.rb:291 0.684
After features/support/hooks.rb:75 0.000