Project Number Date
test_Tails_ISO_stable 5227 28 Oct 2024, 16:37

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:51.078 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:35.420
Before features/support/hooks.rb:269 0.006
Given a computer 0.175
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 30.680
When I start Tails from USB drive "old" with network unplugged 1:59.367
Then the boot device has safe access rights 3.060
And Tails is running from USB drive "old" 0.366
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.111
And udev-watchdog is monitoring the correct device 0.299
And I unplug USB drive "old" 0.199
After features/support/hooks.rb:326 3.755
After features/support/hooks.rb:100 0.010
Tags: @product
2:5.759
Before features/support/hooks.rb:269 0.007
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login 1:19.644
Then Tails is running from USB drive "old" 0.317
And I create a persistent partition 35.071
And I take note of which tps features are available 1.352
Then a Tails persistence partition exists on USB drive "old" 0.831
And I shutdown Tails and wait for the computer to power off 8.348
After features/support/hooks.rb:326 0.195
After features/support/hooks.rb:100 0.010
Tags: @product
2:50.265
Before features/support/hooks.rb:269 0.007
Given a computer 0.184
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.140
Then Tails is running from USB drive "old" 0.394
And all tps features are active 2.422
When I write some files expected to persist 1.951
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.216
And all persistence configuration files have safe access rights 0.412
And all persistent directories from the old Tails version have safe access rights 2.653
And I take note of which tps features are available 0.412
And I shutdown Tails and wait for the computer to power off 4.382
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.096
After features/support/hooks.rb:326 0.162
After features/support/hooks.rb:100 0.008
Tags: @product
2:32.771
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.917
And I log in to a new session 18.603
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.903
And I plug USB drive "to_upgrade" 2.385
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.528
Then the running Tails is installed on USB drive "to_upgrade" 22.019
And I unplug USB drive "to_upgrade" 0.228
And I unplug USB drive "__internal" 0.185
After features/support/hooks.rb:326 1.906
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.603
Before features/support/hooks.rb:269 0.006
Given a computer 0.188
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.800
Then all tps features from the old Tails version are active 1.705
And Tails is running from USB drive "to_upgrade" 0.361
And the boot device has safe access rights 3.835
And the expected persistent files created with the old Tails version are present in the filesystem 1.384
And all persistent directories from the old Tails version have safe access rights 2.329
After features/support/hooks.rb:326 1.129
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:52.379
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.644
And no SquashFS delta is installed 0.170
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.282
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
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.685
When the network is plugged 0.259
And Tor is ready 23.033
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.563
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.177
Given I shutdown Tails and wait for the computer to power off 10.727
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.240
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.308
And the file system changes introduced in version 6.2~testoverlayfs are present 0.361
And only the 6.2~testoverlayfs SquashFS delta is installed 0.085
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.311
# 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.477
When the network is plugged 0.058
And Tor is ready 21.157
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.998
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.979
Given I shutdown Tails and wait for the computer to power off 4.378
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.024
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.273
And the file system changes introduced in version 6.3~testoverlayfs are present 0.481
And only the 6.3~testoverlayfs SquashFS delta is installed 0.056
# 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.303
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.240
When the network is plugged 0.058
And Tor is ready 17.382
Then the Upgrader considers the system as up-to-date 10.790
# 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.347
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.123
After features/support/hooks.rb:326 0.842
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
38.877
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.309
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.354
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 1.170
But a current signing key is available on our website 0.000
When the network is plugged 0.089
And Tor is ready 20.047
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.846
After features/support/hooks.rb:326 1.072
After features/support/hooks.rb:100 0.000