Project Number Date
test_Tails_ISO_stable 4802 20 Apr 2024, 16:32

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 20:18.957 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:10.267
Before features/support/hooks.rb:259 0.004
Given a computer 0.185
And I create a 7200 MiB disk named "old" 0.062
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 32.742
When I start Tails from USB drive "old" with network unplugged 1:32.253
Then the boot device has safe access rights 2.984
And Tails is running from USB drive "old" 0.316
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.291
And I unplug USB drive "old" 0.205
After features/support/hooks.rb:305 7.097
After features/support/hooks.rb:89 0.012
Tags: @product
2:15.577
Before features/support/hooks.rb:259 0.007
Given a computer 0.206
And I start Tails from USB drive "old" with network unplugged and I login 1:23.304
Then Tails is running from USB drive "old" 0.381
And I create a persistent partition 40.570
And I take note of which tps features are available 1.543
Then a Tails persistence partition exists on USB drive "old" 0.890
And I shutdown Tails and wait for the computer to power off 8.680
After features/support/hooks.rb:305 0.174
After features/support/hooks.rb:89 0.010
Tags: @product
2:58.417
Before features/support/hooks.rb:259 0.006
Given a computer 0.251
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.393
Then Tails is running from USB drive "old" 0.339
And all tps features are active 3.757
When I write some files expected to persist 1.727
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.313
And all persistence configuration files have safe access rights 0.436
And all persistent directories from the old Tails version have safe access rights 2.394
And I take note of which tps features are available 0.498
And I shutdown Tails and wait for the computer to power off 4.525
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.780
After features/support/hooks.rb:305 0.134
After features/support/hooks.rb:89 0.012
Tags: @product
2:31.729
Before features/support/hooks.rb:259 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 10.416
And I log in to a new session 22.176
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.619
And I plug USB drive "to_upgrade" 2.500
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.354
Then the running Tails is installed on USB drive "to_upgrade" 19.269
And I unplug USB drive "to_upgrade" 0.214
And I unplug USB drive "__internal" 0.177
After features/support/hooks.rb:305 3.580
After features/support/hooks.rb:89 0.000
Tags: @product
2:17.008
Before features/support/hooks.rb:259 0.008
Given a computer 0.205
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.210
Then all tps features from the old Tails version are active 1.761
And Tails is running from USB drive "to_upgrade" 0.373
And the boot device has safe access rights 3.482
And the expected persistent files created with the old Tails version are present in the filesystem 1.570
And all persistent directories from the old Tails version have safe access rights 2.404
After features/support/hooks.rb:305 0.889
After features/support/hooks.rb:89 0.008
Tags: @product @automatic_upgrade
7:8.008
Before features/support/hooks.rb:259 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.826
And no SquashFS delta is installed 0.074
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.283
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.397
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.556
When the network is plugged 0.035
And Tor is ready 21.564
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.334
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.341
Given I shutdown Tails and wait for the computer to power off 9.228
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.708
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.714
And the file system changes introduced in version 6.2~testoverlayfs are present 0.354
And only the 6.2~testoverlayfs 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.358
# 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.297
When the network is plugged 0.063
And Tor is ready 49.375
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.588
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.154
Given I shutdown Tails and wait for the computer to power off 4.694
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.614
Then Tails is running version 6.3~testoverlayfs 0.168
And all tps features are active 3.878
And the file system changes introduced in version 6.3~testoverlayfs are present 0.690
And only the 6.3~testoverlayfs SquashFS delta is installed 0.104
# 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.336
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.354
When the network is plugged 0.046
And Tor is ready 23.257
Then the Upgrader considers the system as up-to-date 0.391
# 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 16.094
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.962
After features/support/hooks.rb:305 0.791
After features/support/hooks.rb:89 0.020
Tags: @product @automatic_upgrade
57.947
Before features/support/hooks.rb:259 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.000
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.324
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the signing key used by the Upgrader is outdated 0.808
But a current signing key is available on our website 0.000
When the network is plugged 0.049
And Tor is ready 45.107
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.590
After features/support/hooks.rb:305 0.698
After features/support/hooks.rb:89 0.000