Project Number Date
test_Tails_ISO_stable 4622 17 Jan 2024, 12:18

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:29.644 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.991
Before features/support/hooks.rb:245 0.004
Given a computer 0.253
And I create a 7200 MiB disk named "old" 0.076
And I plug USB drive "old" 1.056
And I write an old version of the Tails USB image to disk "old" 28.364
When I start Tails from USB drive "old" with network unplugged 59.589
Then the boot device has safe access rights 3.734
And Tails is running from USB drive "old" 0.297
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.264
And I unplug USB drive "old" 0.197
After features/support/hooks.rb:291 3.537
After features/support/hooks.rb:75 0.060
Tags: @product
1:57.628
Before features/support/hooks.rb:245 0.006
Given a computer 0.170
And I start Tails from USB drive "old" with network unplugged and I login 1:2.940
Then Tails is running from USB drive "old" 0.549
And I create a persistent partition 44.215
And I take note of which tps features are available 1.789
Then a Tails persistence partition exists on USB drive "old" 0.869
And I shutdown Tails and wait for the computer to power off 7.092
After features/support/hooks.rb:291 0.119
After features/support/hooks.rb:75 0.009
Tags: @product
2:15.186
Before features/support/hooks.rb:245 0.006
Given a computer 0.169
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:48.925
Then Tails is running from USB drive "old" 0.358
And all tps features are active 2.051
When I write some files expected to persist 1.688
# 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.586
And all persistent directories from the old Tails version have safe access rights 2.688
And I take note of which tps features are available 0.565
And I shutdown Tails and wait for the computer to power off 3.060
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.841
After features/support/hooks.rb:291 0.138
After features/support/hooks.rb:75 0.009
Tags: @product
2:29.348
Before features/support/hooks.rb:245 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.345
And I log in to a new session 16.608
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.089
And I plug USB drive "to_upgrade" 2.642
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:46.731
Then the running Tails is installed on USB drive "to_upgrade" 12.517
And I unplug USB drive "to_upgrade" 0.203
And I unplug USB drive "__internal" 0.209
After features/support/hooks.rb:291 6.764
After features/support/hooks.rb:75 0.000
Tags: @product
1:53.820
Before features/support/hooks.rb:245 0.006
Given a computer 0.193
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:43.948
Then all tps features from the old Tails version are active 1.706
And Tails is running from USB drive "to_upgrade" 0.343
And the boot device has safe access rights 3.482
And the expected persistent files created with the old Tails version are present in the filesystem 1.495
And all persistent directories from the old Tails version have safe access rights 2.650
After features/support/hooks.rb:291 0.652
After features/support/hooks.rb:75 0.008
Tags: @product @automatic_upgrade
5:51.433
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 10.741
And no SquashFS delta is installed 0.126
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.287
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.065
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.369
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.585
When the network is plugged 0.057
And Tor is ready 17.789
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.680
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.513
Given I shutdown Tails and wait for the computer to power off 5.270
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:47.517
Then Tails is running version 2.2~testoverlayfsng 0.121
And all tps features are active 2.169
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.365
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.268
# 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.260
When the network is plugged 0.054
And Tor is ready 16.838
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.654
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.955
Given I shutdown Tails and wait for the computer to power off 4.659
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.223
Then Tails is running version 2.3~testoverlayfsng 0.100
And all tps features are active 2.014
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.572
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.071
# 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.289
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.317
When the network is plugged 0.034
And Tor is ready 18.637
Then the Upgrader considers the system as up-to-date 0.314
# 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.982
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.450
After features/support/hooks.rb:291 0.722
After features/support/hooks.rb:75 0.017
Tags: @product @automatic_upgrade
28.236
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 9.162
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.326
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.054
And the signing key used by the Upgrader is outdated 1.522
But a current signing key is available on our website 0.000
When the network is plugged 0.071
And Tor is ready 14.543
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.555
After features/support/hooks.rb:291 1.026
After features/support/hooks.rb:75 0.000