Project Number Date
test_Tails_ISO_stable 4628 22 Jan 2024, 15:46

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:30.760 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.204
Before features/support/hooks.rb:245 0.004
Given a computer 0.181
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 20.905
When I start Tails from USB drive "old" with network unplugged 1:1.650
Then the boot device has safe access rights 3.363
And Tails is running from USB drive "old" 0.382
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.066
And udev-watchdog is monitoring the correct device 0.282
And I unplug USB drive "old" 0.218
After features/support/hooks.rb:291 3.806
After features/support/hooks.rb:75 0.009
Tags: @product
2:4.464
Before features/support/hooks.rb:245 0.008
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login 1:6.121
Then Tails is running from USB drive "old" 0.483
And I create a persistent partition 46.288
And I take note of which tps features are available 2.301
Then a Tails persistence partition exists on USB drive "old" 1.001
And I shutdown Tails and wait for the computer to power off 8.082
After features/support/hooks.rb:291 0.141
After features/support/hooks.rb:75 0.010
Tags: @product
2:21.743
Before features/support/hooks.rb:245 0.006
Given a computer 0.981
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:51.288
Then Tails is running from USB drive "old" 0.403
And all tps features are active 2.298
When I write some files expected to persist 1.855
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.265
And all persistence configuration files have safe access rights 0.689
And all persistent directories from the old Tails version have safe access rights 3.231
And I take note of which tps features are available 0.501
And I shutdown Tails and wait for the computer to power off 3.066
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.162
After features/support/hooks.rb:291 0.129
After features/support/hooks.rb:75 0.009
Tags: @product
2:37.784
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.258
And I log in to a new session 18.387
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.399
And I plug USB drive "to_upgrade" 2.494
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:50.565
Then the running Tails is installed on USB drive "to_upgrade" 14.295
And I unplug USB drive "to_upgrade" 0.207
And I unplug USB drive "__internal" 0.177
After features/support/hooks.rb:291 6.616
After features/support/hooks.rb:75 0.000
Tags: @product
2:2.113
Before features/support/hooks.rb:245 0.007
Given a computer 0.193
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:52.143
Then all tps features from the old Tails version are active 1.601
And Tails is running from USB drive "to_upgrade" 0.357
And the boot device has safe access rights 3.387
And the expected persistent files created with the old Tails version are present in the filesystem 1.631
And all persistent directories from the old Tails version have safe access rights 2.799
After features/support/hooks.rb:291 0.752
After features/support/hooks.rb:75 0.010
Tags: @product @automatic_upgrade
6:28.012
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.295
And no SquashFS delta is installed 0.130
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.349
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.082
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.501
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.652
When the network is plugged 0.034
And Tor is ready 18.364
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.659
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.637
Given I shutdown Tails and wait for the computer to power off 6.300
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.303
Then Tails is running version 2.2~testoverlayfsng 0.106
And all tps features are active 2.219
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.405
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.296
# 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.300
When the network is plugged 0.033
And Tor is ready 45.478
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 0.580
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.263
Given I shutdown Tails and wait for the computer to power off 4.079
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.660
Then Tails is running version 2.3~testoverlayfsng 0.132
And all tps features are active 2.144
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.605
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.076
# 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.309
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.365
When the network is plugged 0.039
And Tor is ready 18.482
Then the Upgrader considers the system as up-to-date 0.296
# 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 27.183
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.567
After features/support/hooks.rb:291 0.835
After features/support/hooks.rb:75 0.026
Tags: @product @automatic_upgrade
28.436
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 10.180
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.509
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.092
And the signing key used by the Upgrader is outdated 0.663
But a current signing key is available on our website 0.000
When the network is plugged 0.053
And Tor is ready 15.249
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.687
After features/support/hooks.rb:291 0.663
After features/support/hooks.rb:75 0.000