Project Number Date
test_Tails_ISO_stable 4766 03 Apr 2024, 18:06

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:44.886 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:47.471
Before features/support/hooks.rb:245 0.005
Given a computer 0.221
And I create a 7200 MiB disk named "old" 0.139
And I plug USB drive "old" 1.116
And I write an old version of the Tails USB image to disk "old" 24.337
When I start Tails from USB drive "old" with network unplugged 1:16.636
Then the boot device has safe access rights 3.993
And Tails is running from USB drive "old" 0.316
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.085
And udev-watchdog is monitoring the correct device 0.324
And I unplug USB drive "old" 0.228
After features/support/hooks.rb:291 3.614
After features/support/hooks.rb:75 0.014
Tags: @product
2:12.130
Before features/support/hooks.rb:245 0.008
Given a computer 0.348
And I start Tails from USB drive "old" with network unplugged and I login 1:23.754
Then Tails is running from USB drive "old" 0.373
And I create a persistent partition 36.592
And I take note of which tps features are available 1.417
Then a Tails persistence partition exists on USB drive "old" 0.777
And I shutdown Tails and wait for the computer to power off 8.865
After features/support/hooks.rb:291 0.206
After features/support/hooks.rb:75 0.010
Tags: @product
2:39.765
Before features/support/hooks.rb:245 0.006
Given a computer 0.197
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.781
Then Tails is running from USB drive "old" 0.322
And all tps features are active 1.988
When I write some files expected to persist 1.674
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.200
And all persistence configuration files have safe access rights 0.354
And all persistent directories from the old Tails version have safe access rights 2.392
And I take note of which tps features are available 0.453
And I shutdown Tails and wait for the computer to power off 4.443
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.956
After features/support/hooks.rb:291 0.118
After features/support/hooks.rb:75 0.013
Tags: @product
2:24.434
Before features/support/hooks.rb:245 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.299
And I log in to a new session 16.055
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.608
And I plug USB drive "to_upgrade" 2.496
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.684
Then the running Tails is installed on USB drive "to_upgrade" 14.750
And I unplug USB drive "to_upgrade" 0.299
And I unplug USB drive "__internal" 0.240
After features/support/hooks.rb:291 2.393
After features/support/hooks.rb:75 0.000
Tags: @product
2:10.273
Before features/support/hooks.rb:245 0.008
Given a computer 0.196
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:0.117
Then all tps features from the old Tails version are active 1.933
And Tails is running from USB drive "to_upgrade" 0.346
And the boot device has safe access rights 3.608
And the expected persistent files created with the old Tails version are present in the filesystem 1.432
And all persistent directories from the old Tails version have safe access rights 2.638
After features/support/hooks.rb:291 1.004
After features/support/hooks.rb:75 0.013
Tags: @product @automatic_upgrade
5:59.825
Before features/support/hooks.rb:245 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.506
And no SquashFS delta is installed 0.088
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.316
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.324
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.518
When the network is plugged 0.038
And Tor is ready 18.724
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.374
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.083
Given I shutdown Tails and wait for the computer to power off 6.532
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.249
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.170
And the file system changes introduced in version 6.2~testoverlayfs are present 0.341
And only the 6.2~testoverlayfs SquashFS delta is installed 0.089
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.299
# We'll really install Tails_amd64_6.0~testoverlayfs_to_6.3~testoverlayfs.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 6.1~testoverlayfs was initially installed 0.294
When the network is plugged 0.055
And Tor is ready 19.271
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.645
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.953
Given I shutdown Tails and wait for the computer to power off 4.517
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.768
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.005
And the file system changes introduced in version 6.3~testoverlayfs are present 0.478
And only the 6.3~testoverlayfs 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.293
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.267
When the network is plugged 0.036
And Tor is ready 18.797
Then the Upgrader considers the system as up-to-date 0.244
# 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 14.321
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.052
After features/support/hooks.rb:291 0.884
After features/support/hooks.rb:75 0.022
Tags: @product @automatic_upgrade
30.984
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.393
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.267
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
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.059
And Tor is ready 14.936
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.561
After features/support/hooks.rb:291 0.694
After features/support/hooks.rb:75 0.000