Project Number Date
test_Tails_ISO_devel 3193 13 Dec 2023, 16:53

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:16.047 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:21.649
Before features/support/hooks.rb:245 0.005
Given a computer 0.137
And I create a 7200 MiB disk named "old" 0.026
And I plug USB drive "old" 1.042
And I write an old version of the Tails USB image to disk "old" 19.856
When I start Tails from USB drive "old" with network unplugged 56.543
Then the boot device has safe access rights 3.132
And Tails is running from USB drive "old" 0.318
And there is no persistence partition on USB drive "old" 0.082
And process "udev-watchdog" is running 0.053
And udev-watchdog is monitoring the correct device 0.282
And I unplug USB drive "old" 0.172
After features/support/hooks.rb:291 3.527
After features/support/hooks.rb:75 0.010
Tags: @product
1:52.842
Before features/support/hooks.rb:245 0.006
Given a computer 0.141
And I start Tails from USB drive "old" with network unplugged and I login 59.146
Then Tails is running from USB drive "old" 0.480
And I create a persistent partition 43.602
And I take note of which tps features are available 1.385
Then a Tails persistence partition exists on USB drive "old" 0.888
And I shutdown Tails and wait for the computer to power off 7.197
After features/support/hooks.rb:291 0.094
After features/support/hooks.rb:75 0.010
Tags: @product
2:17.852
Before features/support/hooks.rb:245 0.006
Given a computer 0.139
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:50.439
Then Tails is running from USB drive "old" 0.370
And all tps features are active 1.816
When I write some files expected to persist 1.743
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.255
And all persistence configuration files have safe access rights 0.563
And all persistent directories from the old Tails version have safe access rights 2.772
And I take note of which tps features are available 0.538
And I shutdown Tails and wait for the computer to power off 3.124
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 16.088
After features/support/hooks.rb:291 0.156
After features/support/hooks.rb:75 0.012
Tags: @product
2:31.552
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.674
And I log in to a new session 15.007
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.052
And I plug USB drive "to_upgrade" 2.544
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:49.519
Then the running Tails is installed on USB drive "to_upgrade" 13.364
And I unplug USB drive "to_upgrade" 0.199
And I unplug USB drive "__internal" 0.190
After features/support/hooks.rb:291 6.340
After features/support/hooks.rb:75 0.000
Tags: @product
1:50.396
Before features/support/hooks.rb:245 0.007
Given a computer 0.147
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:41.025
Then all tps features from the old Tails version are active 1.334
And Tails is running from USB drive "to_upgrade" 0.329
And the boot device has safe access rights 3.289
And the expected persistent files created with the old Tails version are present in the filesystem 1.423
And all persistent directories from the old Tails version have safe access rights 2.845
After features/support/hooks.rb:291 0.618
After features/support/hooks.rb:75 0.008
Tags: @product @automatic_upgrade
5:27.589
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 11.028
And no SquashFS delta is installed 0.098
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.284
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.070
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.466
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.473
When the network is plugged 0.063
And Tor is ready 16.452
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.637
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.743
Given I shutdown Tails and wait for the computer to power off 5.286
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:43.516
Then Tails is running version 2.2~testoverlayfsng 0.089
And all tps features are active 2.104
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.407
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.079
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.329
# 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.305
When the network is plugged 0.019
And Tor is ready 13.178
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.675
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.734
Given I shutdown Tails and wait for the computer to power off 3.192
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:43.047
Then Tails is running version 2.3~testoverlayfsng 0.101
And all tps features are active 1.730
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.563
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.275
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.313
When the network is plugged 0.037
And Tor is ready 15.647
Then the Upgrader considers the system as up-to-date 0.309
# 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.006
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.207
After features/support/hooks.rb:291 0.742
After features/support/hooks.rb:75 0.021
Tags: @product @automatic_upgrade
54.163
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.765
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.297
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.087
And the signing key used by the Upgrader is outdated 0.463
But a current signing key is available on our website 0.000
When the network is plugged 0.029
And Tor is ready 42.946
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 0.571
After features/support/hooks.rb:291 0.647
After features/support/hooks.rb:75 0.000