Project Number Date
test_Tails_ISO_stable 5134 02 Oct 2024, 20:01

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 19:14.525 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.897
Before features/support/hooks.rb:269 0.005
Given a computer 0.193
And I create a 7200 MiB disk named "old" 0.038
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 38.343
When I start Tails from USB drive "old" with network unplugged 1:31.966
Then the boot device has safe access rights 3.179
And Tails is running from USB drive "old" 0.341
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.104
And udev-watchdog is monitoring the correct device 0.347
And I unplug USB drive "old" 0.268
After features/support/hooks.rb:326 0.712
After features/support/hooks.rb:100 0.016
Tags: @product
2:15.859
Before features/support/hooks.rb:269 0.005
Given a computer 0.173
And I start Tails from USB drive "old" with network unplugged and I login 1:30.937
Then Tails is running from USB drive "old" 0.364
And I create a persistent partition 33.590
And I take note of which tps features are available 1.462
Then a Tails persistence partition exists on USB drive "old" 0.807
And I shutdown Tails and wait for the computer to power off 8.523
After features/support/hooks.rb:326 0.146
After features/support/hooks.rb:100 0.009
Tags: @product
2:52.447
Before features/support/hooks.rb:269 0.005
Given a computer 0.218
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.223
Then Tails is running from USB drive "old" 0.332
And all tps features are active 2.202
When I write some files expected to persist 1.657
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.195
And all persistence configuration files have safe access rights 0.391
And all persistent directories from the old Tails version have safe access rights 2.366
And I take note of which tps features are available 0.404
And I shutdown Tails and wait for the computer to power off 4.352
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.104
After features/support/hooks.rb:326 0.157
After features/support/hooks.rb:100 0.009
Tags: @product
2:31.839
Before features/support/hooks.rb:269 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 12.796
And I log in to a new session 21.250
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.961
And I plug USB drive "to_upgrade" 2.477
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.721
Then the running Tails is installed on USB drive "to_upgrade" 18.230
And I unplug USB drive "to_upgrade" 0.199
And I unplug USB drive "__internal" 0.203
After features/support/hooks.rb:326 3.095
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.102
Before features/support/hooks.rb:269 0.006
Given a computer 0.177
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.461
Then all tps features from the old Tails version are active 1.597
And Tails is running from USB drive "to_upgrade" 0.403
And the boot device has safe access rights 3.503
And the expected persistent files created with the old Tails version are present in the filesystem 1.454
And all persistent directories from the old Tails version have safe access rights 2.504
After features/support/hooks.rb:326 1.000
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:27.343
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.962
And no SquashFS delta is installed 0.099
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.383
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.463
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.467
When the network is plugged 0.075
And Tor is ready 20.328
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.250
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.828
Given I shutdown Tails and wait for the computer to power off 10.648
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.921
Then Tails is running version 6.2~testoverlayfs 0.021
And all tps features are active 2.141
And the file system changes introduced in version 6.2~testoverlayfs are present 0.314
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.318
# 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.271
When the network is plugged 0.064
And Tor is ready 20.954
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.686
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.410
Given I shutdown Tails and wait for the computer to power off 4.360
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.069
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.972
And the file system changes introduced in version 6.3~testoverlayfs are present 0.631
And only the 6.3~testoverlayfs SquashFS delta is installed 0.081
# 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.471
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.412
When the network is plugged 0.071
And Tor is ready 20.273
Then the Upgrader considers the system as up-to-date 0.350
# 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.781
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.106
After features/support/hooks.rb:326 0.734
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
37.036
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.848
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.643
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.742
But a current signing key is available on our website 0.000
When the network is plugged 0.076
And Tor is ready 18.814
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.837
After features/support/hooks.rb:326 1.301
After features/support/hooks.rb:100 0.000