Project Number Date
test_Tails_ISO_devel 3386 14 May 2024, 12:42

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 21:39.686 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
2:11.081
Before features/support/hooks.rb:259 0.006
Given a computer 0.215
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 31.119
When I start Tails from USB drive "old" with network unplugged 1:34.268
Then the boot device has safe access rights 3.314
And Tails is running from USB drive "old" 0.368
And there is no persistence partition on USB drive "old" 0.091
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.332
And I unplug USB drive "old" 0.175
After features/support/hooks.rb:305 8.551
After features/support/hooks.rb:89 0.011
Tags: @product
2:23.845
Before features/support/hooks.rb:259 0.009
Given a computer 0.206
And I start Tails from USB drive "old" with network unplugged and I login 1:34.295
Then Tails is running from USB drive "old" 0.312
And I create a persistent partition 36.846
And I take note of which tps features are available 1.584
Then a Tails persistence partition exists on USB drive "old" 1.955
And I shutdown Tails and wait for the computer to power off 8.643
After features/support/hooks.rb:305 0.137
After features/support/hooks.rb:89 0.011
Tags: @product
3:6.309
Before features/support/hooks.rb:259 0.008
Given a computer 0.215
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:27.586
Then Tails is running from USB drive "old" 0.461
And all tps features are active 2.364
When I write some files expected to persist 1.985
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.336
And all persistence configuration files have safe access rights 0.726
And all persistent directories from the old Tails version have safe access rights 2.785
And I take note of which tps features are available 0.521
And I shutdown Tails and wait for the computer to power off 4.305
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.020
After features/support/hooks.rb:305 0.152
After features/support/hooks.rb:89 0.011
Tags: @product
2:29.480
Before features/support/hooks.rb:259 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.410
And I log in to a new session 19.332
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.381
And I plug USB drive "to_upgrade" 2.606
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.361
Then the running Tails is installed on USB drive "to_upgrade" 18.975
And I unplug USB drive "to_upgrade" 0.222
And I unplug USB drive "__internal" 0.190
After features/support/hooks.rb:305 4.574
After features/support/hooks.rb:89 0.000
Tags: @product
2:14.634
Before features/support/hooks.rb:259 0.010
Given a computer 0.253
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.136
Then all tps features from the old Tails version are active 1.779
And Tails is running from USB drive "to_upgrade" 0.319
And the boot device has safe access rights 3.765
And the expected persistent files created with the old Tails version are present in the filesystem 1.759
And all persistent directories from the old Tails version have safe access rights 2.620
After features/support/hooks.rb:305 0.761
After features/support/hooks.rb:89 0.014
Tags: @product @automatic_upgrade
8:15.488
Before features/support/hooks.rb:259 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.124
And no SquashFS delta is installed 0.124
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.409
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.280
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.397
When the network is plugged 0.036
And Tor is ready 33.959
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.647
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.737
Given I shutdown Tails and wait for the computer to power off 15.538
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:16.342
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.228
And the file system changes introduced in version 6.2~testoverlayfs are present 0.332
And only the 6.2~testoverlayfs SquashFS delta is installed 0.088
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.305
# 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.283
When the network is plugged 0.035
And Tor is ready 44.592
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.641
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.352
Given I shutdown Tails and wait for the computer to power off 1:4.792
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.748
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.213
And the file system changes introduced in version 6.3~testoverlayfs are present 0.480
And only the 6.3~testoverlayfs SquashFS delta is installed 0.068
# 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.334
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.256
When the network is plugged 0.069
And Tor is ready 18.830
Then the Upgrader considers the system as up-to-date 0.284
# 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.969
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.900
After features/support/hooks.rb:305 0.708
After features/support/hooks.rb:89 0.022
Tags: @product @automatic_upgrade
58.846
Before features/support/hooks.rb:259 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.628
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.320
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.201
And the signing key used by the Upgrader is outdated 1.621
But a current signing key is available on our website 0.000
When the network is plugged 0.076
And Tor is ready 46.415
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.582
After features/support/hooks.rb:305 0.737
After features/support/hooks.rb:89 0.000