Project Number Date
test_Tails_ISO_stable 4576 18 Dec 2023, 22:11

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:0.725 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:20.877
Before features/support/hooks.rb:245 0.005
Given a computer 0.172
And I create a 7200 MiB disk named "old" 0.058
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 19.739
When I start Tails from USB drive "old" with network unplugged 56.273
Then the boot device has safe access rights 2.722
And Tails is running from USB drive "old" 0.316
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.044
And udev-watchdog is monitoring the correct device 0.256
And I unplug USB drive "old" 0.179
After features/support/hooks.rb:291 3.686
After features/support/hooks.rb:75 0.009
Tags: @product
1:51.678
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 59.419
Then Tails is running from USB drive "old" 0.389
And I create a persistent partition 42.345
And I take note of which tps features are available 1.377
Then a Tails persistence partition exists on USB drive "old" 0.893
And I shutdown Tails and wait for the computer to power off 7.089
After features/support/hooks.rb:291 0.125
After features/support/hooks.rb:75 0.009
Tags: @product
2:17.345
Before features/support/hooks.rb:245 0.005
Given a computer 0.199
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:51.472
Then Tails is running from USB drive "old" 0.346
And all tps features are active 2.213
When I write some files expected to persist 1.678
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.220
And all persistence configuration files have safe access rights 0.623
And all persistent directories from the old Tails version have safe access rights 2.522
And I take note of which tps features are available 0.512
And I shutdown Tails and wait for the computer to power off 3.060
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.496
After features/support/hooks.rb:291 0.112
After features/support/hooks.rb:75 0.011
Tags: @product
2:28.475
Before features/support/hooks.rb:245 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.285
And I log in to a new session 16.268
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.994
And I plug USB drive "to_upgrade" 2.550
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:47.478
Then the running Tails is installed on USB drive "to_upgrade" 11.522
And I unplug USB drive "to_upgrade" 0.195
And I unplug USB drive "__internal" 0.179
After features/support/hooks.rb:291 6.592
After features/support/hooks.rb:75 0.000
Tags: @product
1:53.462
Before features/support/hooks.rb:245 0.006
Given a computer 0.192
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:43.057
Then all tps features from the old Tails version are active 1.712
And Tails is running from USB drive "to_upgrade" 0.347
And the boot device has safe access rights 3.624
And the expected persistent files created with the old Tails version are present in the filesystem 1.499
And all persistent directories from the old Tails version have safe access rights 3.028
After features/support/hooks.rb:291 0.656
After features/support/hooks.rb:75 0.009
Tags: @product @automatic_upgrade
5:42.301
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.954
And no SquashFS delta is installed 0.082
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.395
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.079
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.380
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.575
When the network is plugged 0.043
And Tor is ready 18.933
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.584
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 7.992
Given I shutdown Tails and wait for the computer to power off 6.190
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.892
Then Tails is running version 2.2~testoverlayfsng 0.084
And all tps features are active 2.245
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.367
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.064
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.272
# 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.279
When the network is plugged 0.044
And Tor is ready 17.381
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 0.547
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.069
Given I shutdown Tails and wait for the computer to power off 4.076
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:44.872
Then Tails is running version 2.3~testoverlayfsng 0.095
And all tps features are active 2.266
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.585
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.071
# 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.269
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.285
When the network is plugged 0.052
And Tor is ready 14.869
Then the Upgrader considers the system as up-to-date 0.263
# 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 24.649
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.479
After features/support/hooks.rb:291 0.806
After features/support/hooks.rb:75 0.018
Tags: @product @automatic_upgrade
26.584
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 9.630
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.447
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.081
And the signing key used by the Upgrader is outdated 0.699
But a current signing key is available on our website 0.000
When the network is plugged 0.037
And Tor is ready 13.093
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.593
After features/support/hooks.rb:291 0.838
After features/support/hooks.rb:75 0.000