Project Number Date
test_Tails_ISO_devel 3403 28 May 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 21:18.870 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:15.470
Before features/support/hooks.rb:259 0.027
Given a computer 0.271
And I create a 7200 MiB disk named "old" 0.057
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 30.224
When I start Tails from USB drive "old" with network unplugged 1:39.502
Then the boot device has safe access rights 3.311
And Tails is running from USB drive "old" 0.339
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.107
And udev-watchdog is monitoring the correct device 0.325
And I unplug USB drive "old" 0.207
After features/support/hooks.rb:305 3.565
After features/support/hooks.rb:89 0.010
Tags: @product
2:13.611
Before features/support/hooks.rb:259 0.006
Given a computer 0.245
And I start Tails from USB drive "old" with network unplugged and I login 1:27.158
Then Tails is running from USB drive "old" 0.308
And I create a persistent partition 34.967
And I take note of which tps features are available 1.881
Then a Tails persistence partition exists on USB drive "old" 0.778
And I shutdown Tails and wait for the computer to power off 8.269
After features/support/hooks.rb:305 0.201
After features/support/hooks.rb:89 0.018
Tags: @product
2:49.006
Before features/support/hooks.rb:259 0.012
Given a computer 0.239
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:10.818
Then Tails is running from USB drive "old" 0.319
And all tps features are active 1.988
When I write some files expected to persist 1.812
# 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.413
And all persistent directories from the old Tails version have safe access rights 2.742
And I take note of which tps features are available 0.536
And I shutdown Tails and wait for the computer to power off 4.369
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.510
After features/support/hooks.rb:305 0.176
After features/support/hooks.rb:89 0.010
Tags: @product
2:36.478
Before features/support/hooks.rb:259 0.009
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.762
And I log in to a new session 23.674
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.451
And I plug USB drive "to_upgrade" 2.522
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.096
Then the running Tails is installed on USB drive "to_upgrade" 17.577
And I unplug USB drive "to_upgrade" 0.187
And I unplug USB drive "__internal" 0.204
After features/support/hooks.rb:305 3.647
After features/support/hooks.rb:89 0.000
Tags: @product
2:27.938
Before features/support/hooks.rb:259 0.006
Given a computer 0.197
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:17.575
Then all tps features from the old Tails version are active 1.832
And Tails is running from USB drive "to_upgrade" 0.414
And the boot device has safe access rights 3.547
And the expected persistent files created with the old Tails version are present in the filesystem 1.711
And all persistent directories from the old Tails version have safe access rights 2.659
After features/support/hooks.rb:305 0.621
After features/support/hooks.rb:89 0.011
Tags: @product @automatic_upgrade
7:52.215
Before features/support/hooks.rb:259 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.008
And no SquashFS delta is installed 0.152
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.304
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.083
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.309
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.535
When the network is plugged 0.045
And Tor is ready 23.425
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.079
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.315
Given I shutdown Tails and wait for the computer to power off 9.418
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.509
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 3.246
And the file system changes introduced in version 6.2~testoverlayfs are present 0.360
And only the 6.2~testoverlayfs SquashFS delta is installed 0.100
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.416
# 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.433
When the network is plugged 0.048
And Tor is ready 14.661
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.721
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.624
Given I shutdown Tails and wait for the computer to power off 1:0.632
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.696
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.316
And the file system changes introduced in version 6.3~testoverlayfs are present 0.760
And only the 6.3~testoverlayfs SquashFS delta is installed 0.105
# 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.347
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.336
When the network is plugged 0.051
And Tor is ready 14.999
Then the Upgrader considers the system as up-to-date 10.940
# 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.061
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.135
After features/support/hooks.rb:305 0.912
After features/support/hooks.rb:89 0.028
Tags: @product @automatic_upgrade
1:4.149
Before features/support/hooks.rb:259 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.906
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.459
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the signing key used by the Upgrader is outdated 0.539
But a current signing key is available on our website 0.000
When the network is plugged 0.065
And Tor is ready 49.345
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.763
After features/support/hooks.rb:305 0.928
After features/support/hooks.rb:89 0.000