Project Number Date
test_Tails_ISO_stable 4552 05 Dec 2023, 15:24

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.117 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:37.651
Before features/support/hooks.rb:245 0.006
Given a computer 0.150
And I create a 7200 MiB disk named "old" 0.030
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 21.301
When I start Tails from USB drive "old" with network unplugged 1:10.982
Then the boot device has safe access rights 3.162
And Tails is running from USB drive "old" 0.359
And there is no persistence partition on USB drive "old" 0.056
And process "udev-watchdog" is running 0.059
And udev-watchdog is monitoring the correct device 0.295
And I unplug USB drive "old" 0.204
After features/support/hooks.rb:291 3.546
After features/support/hooks.rb:75 0.013
Tags: @product
2:2.473
Before features/support/hooks.rb:245 0.006
Given a computer 0.151
And I start Tails from USB drive "old" with network unplugged and I login 1:6.548
Then Tails is running from USB drive "old" 0.509
And I create a persistent partition 44.568
And I take note of which tps features are available 1.679
Then a Tails persistence partition exists on USB drive "old" 0.891
And I shutdown Tails and wait for the computer to power off 8.124
After features/support/hooks.rb:291 0.183
After features/support/hooks.rb:75 0.010
Tags: @product
2:24.562
Before features/support/hooks.rb:245 0.006
Given a computer 0.182
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:55.799
Then Tails is running from USB drive "old" 0.503
And all tps features are active 1.980
When I write some files expected to persist 2.110
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.282
And all persistence configuration files have safe access rights 0.806
And all persistent directories from the old Tails version have safe access rights 3.095
And I take note of which tps features are available 0.343
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" 16.391
After features/support/hooks.rb:291 0.107
After features/support/hooks.rb:75 0.009
Tags: @product
2:40.770
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 14.373
And I log in to a new session 18.455
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.577
And I plug USB drive "to_upgrade" 2.519
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:48.782
Then the running Tails is installed on USB drive "to_upgrade" 14.626
And I unplug USB drive "to_upgrade" 0.228
And I unplug USB drive "__internal" 0.207
After features/support/hooks.rb:291 1.828
After features/support/hooks.rb:75 0.000
Tags: @product
1:59.437
Before features/support/hooks.rb:245 0.007
Given a computer 0.150
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:49.533
Then all tps features from the old Tails version are active 1.633
And Tails is running from USB drive "to_upgrade" 0.352
And the boot device has safe access rights 3.414
And the expected persistent files created with the old Tails version are present in the filesystem 1.531
And all persistent directories from the old Tails version have safe access rights 2.822
After features/support/hooks.rb:291 0.714
After features/support/hooks.rb:75 0.010
Tags: @product @automatic_upgrade
5:56.681
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 12.127
And no SquashFS delta is installed 0.265
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.365
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.086
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.371
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.617
When the network is plugged 0.028
And Tor is ready 17.419
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.748
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.697
Given I shutdown Tails and wait for the computer to power off 7.295
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:50.144
Then Tails is running version 2.2~testoverlayfsng 0.101
And all tps features are active 1.924
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.437
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.086
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.325
# 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.022
And Tor is ready 19.145
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.676
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 9.063
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:50.125
Then Tails is running version 2.3~testoverlayfsng 0.145
And all tps features are active 1.897
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.653
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.110
# 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.314
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.338
When the network is plugged 0.032
And Tor is ready 18.967
Then the Upgrader considers the system as up-to-date 0.307
# 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.023
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.235
After features/support/hooks.rb:291 0.765
After features/support/hooks.rb:75 0.019
Tags: @product @automatic_upgrade
26.539
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.861
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.372
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.089
And the signing key used by the Upgrader is outdated 0.738
But a current signing key is available on our website 0.000
When the network is plugged 0.024
And Tor is ready 12.533
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.919
After features/support/hooks.rb:291 0.737
After features/support/hooks.rb:75 0.000