Project Number Date
test_Tails_ISO_stable 4682 26 Feb 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 17:19.813 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:23.743
Before features/support/hooks.rb:245 0.007
Given a computer 0.175
And I create a 7200 MiB disk named "old" 0.055
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 19.588
When I start Tails from USB drive "old" with network unplugged 58.516
Then the boot device has safe access rights 3.288
And Tails is running from USB drive "old" 0.373
And there is no persistence partition on USB drive "old" 0.082
And process "udev-watchdog" is running 0.079
And udev-watchdog is monitoring the correct device 0.316
And I unplug USB drive "old" 0.218
After features/support/hooks.rb:291 3.564
After features/support/hooks.rb:75 0.040
Tags: @product
2:1.767
Before features/support/hooks.rb:245 0.007
Given a computer 0.255
And I start Tails from USB drive "old" with network unplugged and I login 1:6.826
Then Tails is running from USB drive "old" 0.560
And I create a persistent partition 44.283
And I take note of which tps features are available 1.770
Then a Tails persistence partition exists on USB drive "old" 0.979
And I shutdown Tails and wait for the computer to power off 7.091
After features/support/hooks.rb:291 0.156
After features/support/hooks.rb:75 0.013
Tags: @product
2:29.428
Before features/support/hooks.rb:245 0.006
Given a computer 0.252
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:0.331
Then Tails is running from USB drive "old" 0.514
And all tps features are active 2.502
When I write some files expected to persist 2.117
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.295
And all persistence configuration files have safe access rights 0.530
And all persistent directories from the old Tails version have safe access rights 3.440
And I take note of which tps features are available 0.453
And I shutdown Tails and wait for the computer to power off 3.126
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.863
After features/support/hooks.rb:291 0.102
After features/support/hooks.rb:75 0.013
Tags: @product
2:54.543
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 25.027
And I log in to a new session 16.511
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.709
And I plug USB drive "to_upgrade" 2.426
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:51.514
Then the running Tails is installed on USB drive "to_upgrade" 16.901
And I unplug USB drive "to_upgrade" 0.226
And I unplug USB drive "__internal" 0.225
After features/support/hooks.rb:291 1.944
After features/support/hooks.rb:75 0.000
Tags: @product
2:0.654
Before features/support/hooks.rb:245 0.013
Given a computer 0.223
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:49.030
Then all tps features from the old Tails version are active 1.714
And Tails is running from USB drive "to_upgrade" 0.362
And the boot device has safe access rights 4.032
And the expected persistent files created with the old Tails version are present in the filesystem 1.814
And all persistent directories from the old Tails version have safe access rights 3.476
After features/support/hooks.rb:291 1.157
After features/support/hooks.rb:75 0.009
Tags: @product @automatic_upgrade
6:0.503
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.486
And no SquashFS delta is installed 0.391
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 1.503
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.085
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.499
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.643
When the network is plugged 0.341
And Tor is ready 17.260
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.839
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 10.473
Given I shutdown Tails and wait for the computer to power off 6.491
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.301
Then Tails is running version 2.2~testoverlayfsng 0.162
And all tps features are active 2.555
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.424
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.328
# 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.341
When the network is plugged 0.048
And Tor is ready 16.669
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.696
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 10.192
Given I shutdown Tails and wait for the computer to power off 4.443
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.700
Then Tails is running version 2.3~testoverlayfsng 0.159
And all tps features are active 2.277
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.786
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.108
# 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.329
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.337
When the network is plugged 0.035
And Tor is ready 19.592
Then the Upgrader considers the system as up-to-date 0.267
# 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 27.226
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.428
After features/support/hooks.rb:291 0.746
After features/support/hooks.rb:75 0.021
Tags: @product @automatic_upgrade
29.172
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 11.038
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.448
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.075
And the signing key used by the Upgrader is outdated 0.691
But a current signing key is available on our website 0.000
When the network is plugged 0.042
And Tor is ready 13.861
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 3.013
After features/support/hooks.rb:291 0.710
After features/support/hooks.rb:75 0.000