Project Number Date
test_Tails_ISO_stable 4634 24 Jan 2024, 17: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 16:41.062 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:22.775
Before features/support/hooks.rb:245 0.005
Given a computer 0.145
And I create a 7200 MiB disk named "old" 0.029
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 22.611
When I start Tails from USB drive "old" with network unplugged 55.163
Then the boot device has safe access rights 2.910
And Tails is running from USB drive "old" 0.310
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.059
And udev-watchdog is monitoring the correct device 0.253
And I unplug USB drive "old" 0.174
After features/support/hooks.rb:291 3.534
After features/support/hooks.rb:75 0.010
Tags: @product
1:53.453
Before features/support/hooks.rb:245 0.006
Given a computer 0.134
And I start Tails from USB drive "old" with network unplugged and I login 1:1.132
Then Tails is running from USB drive "old" 0.437
And I create a persistent partition 42.586
And I take note of which tps features are available 1.238
Then a Tails persistence partition exists on USB drive "old" 0.820
And I shutdown Tails and wait for the computer to power off 7.103
After features/support/hooks.rb:291 0.145
After features/support/hooks.rb:75 0.009
Tags: @product
2:21.375
Before features/support/hooks.rb:245 0.006
Given a computer 0.155
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:55.826
Then Tails is running from USB drive "old" 0.343
And all tps features are active 1.851
When I write some files expected to persist 1.831
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.248
And all persistence configuration files have safe access rights 0.431
And all persistent directories from the old Tails version have safe access rights 2.652
And I take note of which tps features are available 0.382
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" 14.585
After features/support/hooks.rb:291 0.152
After features/support/hooks.rb:75 0.009
Tags: @product
2:31.488
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 10.001
And I log in to a new session 15.446
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.205
And I plug USB drive "to_upgrade" 2.494
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:49.490
Then the running Tails is installed on USB drive "to_upgrade" 12.482
And I unplug USB drive "to_upgrade" 0.184
And I unplug USB drive "__internal" 0.183
After features/support/hooks.rb:291 0.842
After features/support/hooks.rb:75 0.000
Tags: @product
2:4.464
Before features/support/hooks.rb:245 0.006
Given a computer 0.134
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:54.160
Then all tps features from the old Tails version are active 1.582
And Tails is running from USB drive "to_upgrade" 0.345
And the boot device has safe access rights 3.727
And the expected persistent files created with the old Tails version are present in the filesystem 1.713
And all persistent directories from the old Tails version have safe access rights 2.799
After features/support/hooks.rb:291 0.857
After features/support/hooks.rb:75 0.009
Tags: @product @automatic_upgrade
5:54.782
Before features/support/hooks.rb:245 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.457
And no SquashFS delta is installed 0.076
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.275
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.062
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.350
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.582
When the network is plugged 0.022
And Tor is ready 17.372
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.661
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.289
Given I shutdown Tails and wait for the computer to power off 5.271
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.021
Then Tails is running version 2.2~testoverlayfsng 0.106
And all tps features are active 2.080
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.467
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.081
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.292
# 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.321
When the network is plugged 0.027
And Tor is ready 15.379
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.770
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 10.650
Given I shutdown Tails and wait for the computer to power off 4.566
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.386
Then Tails is running version 2.3~testoverlayfsng 0.128
And all tps features are active 2.260
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.662
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.074
# 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.318
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.410
When the network is plugged 0.058
And Tor is ready 16.933
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 26.224
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.841
After features/support/hooks.rb:291 0.802
After features/support/hooks.rb:75 0.017
Tags: @product @automatic_upgrade
32.722
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 14.394
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.346
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.057
And the signing key used by the Upgrader is outdated 1.272
But a current signing key is available on our website 0.000
When the network is plugged 0.045
And Tor is ready 13.917
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.688
After features/support/hooks.rb:291 0.703
After features/support/hooks.rb:75 0.000