Project Number Date
test_Tails_ISO_stable 4659 09 Feb 2024, 18:31

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:45.009 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:26.196
Before features/support/hooks.rb:245 0.007
Given a computer 0.156
And I create a 7200 MiB disk named "old" 0.059
And I plug USB drive "old" 1.045
And I write an old version of the Tails USB image to disk "old" 19.398
When I start Tails from USB drive "old" with network unplugged 1:1.434
Then the boot device has safe access rights 3.222
And Tails is running from USB drive "old" 0.314
And there is no persistence partition on USB drive "old" 0.056
And process "udev-watchdog" is running 0.056
And udev-watchdog is monitoring the correct device 0.271
And I unplug USB drive "old" 0.180
After features/support/hooks.rb:291 3.526
After features/support/hooks.rb:75 0.010
Tags: @product
1:58.285
Before features/support/hooks.rb:245 0.007
Given a computer 0.191
And I start Tails from USB drive "old" with network unplugged and I login 1:4.713
Then Tails is running from USB drive "old" 0.432
And I create a persistent partition 42.588
And I take note of which tps features are available 1.432
Then a Tails persistence partition exists on USB drive "old" 0.865
And I shutdown Tails and wait for the computer to power off 8.062
After features/support/hooks.rb:291 0.127
After features/support/hooks.rb:75 0.009
Tags: @product
2:19.587
Before features/support/hooks.rb:245 0.005
Given a computer 0.164
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:50.904
Then Tails is running from USB drive "old" 0.443
And all tps features are active 2.246
When I write some files expected to persist 1.927
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.246
And all persistence configuration files have safe access rights 0.485
And all persistent directories from the old Tails version have safe access rights 3.083
And I take note of which tps features are available 0.434
And I shutdown Tails and wait for the computer to power off 3.180
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 16.470
After features/support/hooks.rb:291 0.148
After features/support/hooks.rb:75 0.009
Tags: @product
2:33.577
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.800
And I log in to a new session 16.983
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.166
And I plug USB drive "to_upgrade" 2.439
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:49.026
Then the running Tails is installed on USB drive "to_upgrade" 13.794
And I unplug USB drive "to_upgrade" 0.193
And I unplug USB drive "__internal" 0.174
After features/support/hooks.rb:291 4.416
After features/support/hooks.rb:75 0.000
Tags: @product
1:59.067
Before features/support/hooks.rb:245 0.008
Given a computer 0.167
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:49.040
Then all tps features from the old Tails version are active 1.698
And Tails is running from USB drive "to_upgrade" 0.391
And the boot device has safe access rights 3.504
And the expected persistent files created with the old Tails version are present in the filesystem 1.541
And all persistent directories from the old Tails version have safe access rights 2.723
After features/support/hooks.rb:291 0.728
After features/support/hooks.rb:75 0.028
Tags: @product @automatic_upgrade
5:57.558
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.307
And no SquashFS delta is installed 0.116
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.397
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.069
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.411
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.563
When the network is plugged 0.058
And Tor is ready 20.668
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.715
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.192
Given I shutdown Tails and wait for the computer to power off 5.393
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.045
Then Tails is running version 2.2~testoverlayfsng 0.127
And all tps features are active 2.288
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.463
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.080
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.289
# 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.352
When the network is plugged 0.044
And Tor is ready 15.504
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.692
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.082
Given I shutdown Tails and wait for the computer to power off 3.617
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:46.741
Then Tails is running version 2.3~testoverlayfsng 0.179
And all tps features are active 2.151
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.672
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.066
# 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.326
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.296
When the network is plugged 0.057
And Tor is ready 14.444
Then the Upgrader considers the system as up-to-date 10.733
# 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.497
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.910
After features/support/hooks.rb:291 0.748
After features/support/hooks.rb:75 0.052
Tags: @product @automatic_upgrade
30.737
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.069
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.413
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.058
And the signing key used by the Upgrader is outdated 0.964
But a current signing key is available on our website 0.000
When the network is plugged 0.034
And Tor is ready 16.389
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.806
After features/support/hooks.rb:291 1.275
After features/support/hooks.rb:75 0.000