Project Number Date
test_Tails_ISO_devel 3241 18 Jan 2024, 12:25

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:46.957 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:19.019
Before features/support/hooks.rb:245 0.007
Given a computer 0.179
And I create a 7200 MiB disk named "old" 0.026
And I plug USB drive "old" 1.044
And I write an old version of the Tails USB image to disk "old" 18.785
When I start Tails from USB drive "old" with network unplugged 55.296
Then the boot device has safe access rights 2.854
And Tails is running from USB drive "old" 0.298
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.060
And udev-watchdog is monitoring the correct device 0.245
And I unplug USB drive "old" 0.169
After features/support/hooks.rb:291 3.459
After features/support/hooks.rb:75 0.037
Tags: @product
1:53.517
Before features/support/hooks.rb:245 0.007
Given a computer 0.136
And I start Tails from USB drive "old" with network unplugged and I login 1:2.216
Then Tails is running from USB drive "old" 0.424
And I create a persistent partition 41.600
And I take note of which tps features are available 1.190
Then a Tails persistence partition exists on USB drive "old" 0.889
And I shutdown Tails and wait for the computer to power off 7.060
After features/support/hooks.rb:291 0.152
After features/support/hooks.rb:75 0.010
Tags: @product
2:15.499
Before features/support/hooks.rb:245 0.007
Given a computer 0.152
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:50.014
Then Tails is running from USB drive "old" 0.335
And all tps features are active 1.625
When I write some files expected to persist 1.894
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.241
And all persistence configuration files have safe access rights 0.652
And all persistent directories from the old Tails version have safe access rights 2.821
And I take note of which tps features are available 0.285
And I shutdown Tails and wait for the computer to power off 3.061
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.413
After features/support/hooks.rb:291 0.095
After features/support/hooks.rb:75 0.010
Tags: @product
2:28.608
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.530
And I log in to a new session 14.089
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.244
And I plug USB drive "to_upgrade" 2.432
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:48.169
Then the running Tails is installed on USB drive "to_upgrade" 12.793
And I unplug USB drive "to_upgrade" 0.180
And I unplug USB drive "__internal" 0.167
After features/support/hooks.rb:291 6.539
After features/support/hooks.rb:75 0.000
Tags: @product
1:47.545
Before features/support/hooks.rb:245 0.007
Given a computer 0.144
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:38.527
Then all tps features from the old Tails version are active 1.455
And Tails is running from USB drive "to_upgrade" 0.295
And the boot device has safe access rights 3.316
And the expected persistent files created with the old Tails version are present in the filesystem 1.431
And all persistent directories from the old Tails version have safe access rights 2.374
After features/support/hooks.rb:291 0.624
After features/support/hooks.rb:75 0.010
Tags: @product @automatic_upgrade
5:37.234
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.699
And no SquashFS delta is installed 0.083
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.291
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.059
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.333
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.475
When the network is plugged 0.020
And Tor is ready 15.169
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.604
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 7.326
Given I shutdown Tails and wait for the computer to power off 5.328
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:44.708
Then Tails is running version 2.2~testoverlayfsng 0.089
And all tps features are active 1.725
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.303
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.063
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.255
# 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.030
And Tor is ready 15.788
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.554
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.566
Given I shutdown Tails and wait for the computer to power off 4.140
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:44.809
Then Tails is running version 2.3~testoverlayfsng 0.086
And all tps features are active 1.702
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.564
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.083
# 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.275
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.303
When the network is plugged 0.027
And Tor is ready 13.303
Then the Upgrader considers the system as up-to-date 10.680
# 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.804
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.712
After features/support/hooks.rb:291 0.756
After features/support/hooks.rb:75 0.020
Tags: @product @automatic_upgrade
25.533
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.379
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.259
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.047
And the signing key used by the Upgrader is outdated 1.001
But a current signing key is available on our website 0.000
When the network is plugged 0.026
And Tor is ready 13.126
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.693
After features/support/hooks.rb:291 0.657
After features/support/hooks.rb:75 0.000