Project Number Date
test_Tails_ISO_stable 4681 25 Feb 2024, 12:17

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:45.699 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:34.058
Before features/support/hooks.rb:245 0.007
Given a computer 0.198
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.060
And I write an old version of the Tails USB image to disk "old" 27.106
When I start Tails from USB drive "old" with network unplugged 1:1.469
Then the boot device has safe access rights 3.248
And Tails is running from USB drive "old" 0.307
And there is no persistence partition on USB drive "old" 0.080
And process "udev-watchdog" is running 0.059
And udev-watchdog is monitoring the correct device 0.271
And I unplug USB drive "old" 0.208
After features/support/hooks.rb:291 3.576
After features/support/hooks.rb:75 0.008
Tags: @product
2:2.587
Before features/support/hooks.rb:245 0.005
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login 1:7.600
Then Tails is running from USB drive "old" 0.343
And I create a persistent partition 43.828
And I take note of which tps features are available 1.517
Then a Tails persistence partition exists on USB drive "old" 0.919
And I shutdown Tails and wait for the computer to power off 8.186
After features/support/hooks.rb:291 0.163
After features/support/hooks.rb:75 0.012
Tags: @product
2:18.440
Before features/support/hooks.rb:245 0.006
Given a computer 0.251
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:51.329
Then Tails is running from USB drive "old" 0.407
And all tps features are active 2.152
When I write some files expected to persist 1.905
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.288
And all persistence configuration files have safe access rights 0.427
And all persistent directories from the old Tails version have safe access rights 2.733
And I take note of which tps features are available 0.563
And I shutdown Tails and wait for the computer to power off 3.076
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.305
After features/support/hooks.rb:291 0.103
After features/support/hooks.rb:75 0.010
Tags: @product
2:43.050
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.350
And I log in to a new session 22.668
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.245
And I plug USB drive "to_upgrade" 2.552
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:53.538
Then the running Tails is installed on USB drive "to_upgrade" 13.307
And I unplug USB drive "to_upgrade" 0.197
And I unplug USB drive "__internal" 0.191
After features/support/hooks.rb:291 6.839
After features/support/hooks.rb:75 0.000
Tags: @product
2:9.274
Before features/support/hooks.rb:245 0.006
Given a computer 0.240
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:57.616
Then all tps features from the old Tails version are active 1.972
And Tails is running from USB drive "to_upgrade" 0.425
And the boot device has safe access rights 4.020
And the expected persistent files created with the old Tails version are present in the filesystem 2.033
And all persistent directories from the old Tails version have safe access rights 2.964
After features/support/hooks.rb:291 0.700
After features/support/hooks.rb:75 0.010
Tags: @product @automatic_upgrade
6:1.121
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.506
And no SquashFS delta is installed 0.295
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.343
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.099
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.465
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.683
When the network is plugged 0.802
And Tor is ready 17.130
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.728
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.483
Given I shutdown Tails and wait for the computer to power off 6.412
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.846
Then Tails is running version 2.2~testoverlayfsng 0.122
And all tps features are active 2.605
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.474
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.083
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.348
# 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.359
When the network is plugged 0.129
And Tor is ready 17.326
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 0.627
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 9.390
Given I shutdown Tails and wait for the computer to power off 4.065
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:48.660
Then Tails is running version 2.3~testoverlayfsng 0.135
And all tps features are active 2.344
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.689
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.086
# 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.277
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.316
When the network is plugged 0.083
And Tor is ready 16.254
Then the Upgrader considers the system as up-to-date 0.318
# 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 31.298
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.324
After features/support/hooks.rb:291 0.781
After features/support/hooks.rb:75 0.023
Tags: @product @automatic_upgrade
57.166
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.147
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.336
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.072
And the signing key used by the Upgrader is outdated 1.052
But a current signing key is available on our website 0.000
When the network is plugged 0.142
And Tor is ready 43.749
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 0.665
After features/support/hooks.rb:291 1.115
After features/support/hooks.rb:75 0.000