Project Number Date
test_Tails_ISO_devel 3498 31 Aug 2024, 12:41

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 18:38.633 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:3.872
Before features/support/hooks.rb:269 0.007
Given a computer 0.199
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 28.701
When I start Tails from USB drive "old" with network unplugged 1:29.877
Then the boot device has safe access rights 3.040
And Tails is running from USB drive "old" 0.308
And there is no persistence partition on USB drive "old" 0.086
And process "udev-watchdog" is running 0.087
And udev-watchdog is monitoring the correct device 0.287
And I unplug USB drive "old" 0.185
After features/support/hooks.rb:326 3.547
After features/support/hooks.rb:100 0.011
Tags: @product
2:5.658
Before features/support/hooks.rb:269 0.007
Given a computer 0.191
And I start Tails from USB drive "old" with network unplugged and I login 1:23.925
Then Tails is running from USB drive "old" 0.323
And I create a persistent partition 30.933
And I take note of which tps features are available 1.396
Then a Tails persistence partition exists on USB drive "old" 0.754
And I shutdown Tails and wait for the computer to power off 8.134
After features/support/hooks.rb:326 0.196
After features/support/hooks.rb:100 0.011
Tags: @product
2:42.490
Before features/support/hooks.rb:269 0.008
Given a computer 0.218
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:4.983
Then Tails is running from USB drive "old" 0.402
And all tps features are active 2.130
When I write some files expected to persist 1.781
# 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.593
And all persistent directories from the old Tails version have safe access rights 2.437
And I take note of which tps features are available 0.481
And I shutdown Tails and wait for the computer to power off 4.685
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.520
After features/support/hooks.rb:326 0.107
After features/support/hooks.rb:100 0.011
Tags: @product
2:35.967
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 23.103
And I log in to a new session 16.923
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.465
And I plug USB drive "to_upgrade" 2.374
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.448
Then the running Tails is installed on USB drive "to_upgrade" 17.225
And I unplug USB drive "to_upgrade" 0.203
And I unplug USB drive "__internal" 0.221
After features/support/hooks.rb:326 2.113
After features/support/hooks.rb:100 0.000
Tags: @product
2:10.160
Before features/support/hooks.rb:269 0.006
Given a computer 0.217
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:0.611
Then all tps features from the old Tails version are active 1.571
And Tails is running from USB drive "to_upgrade" 0.319
And the boot device has safe access rights 3.138
And the expected persistent files created with the old Tails version are present in the filesystem 1.755
And all persistent directories from the old Tails version have safe access rights 2.546
After features/support/hooks.rb:326 0.804
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:24.130
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.830
And no SquashFS delta is installed 0.168
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.307
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.303
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.614
When the network is plugged 0.071
And Tor is ready 19.005
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.138
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.257
Given I shutdown Tails and wait for the computer to power off 10.728
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.017
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.063
And the file system changes introduced in version 6.2~testoverlayfs are present 0.273
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.336
# 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.256
When the network is plugged 0.084
And Tor is ready 18.466
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.190
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.819
Given I shutdown Tails and wait for the computer to power off 4.306
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.930
Then Tails is running version 6.3~testoverlayfs 0.039
And all tps features are active 1.963
And the file system changes introduced in version 6.3~testoverlayfs are present 0.467
And only the 6.3~testoverlayfs SquashFS delta is installed 0.061
# 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.401
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.292
When the network is plugged 0.077
And Tor is ready 18.672
Then the Upgrader considers the system as up-to-date 0.346
# 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 13.450
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.050
After features/support/hooks.rb:326 0.668
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
36.352
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.567
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.714
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the signing key used by the Upgrader is outdated 1.120
But a current signing key is available on our website 0.000
When the network is plugged 0.066
And Tor is ready 18.315
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.511
After features/support/hooks.rb:326 1.891
After features/support/hooks.rb:100 0.000