Project Number Date
test_Tails_ISO_stable 5012 08 Aug 2024, 14:12

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:50.978 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:28.496
Before features/support/hooks.rb:269 0.008
Given a computer 0.185
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 31.046
When I start Tails from USB drive "old" with network unplugged 1:52.004
Then the boot device has safe access rights 3.169
And Tails is running from USB drive "old" 0.349
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.095
And udev-watchdog is monitoring the correct device 0.289
And I unplug USB drive "old" 0.197
After features/support/hooks.rb:326 7.094
After features/support/hooks.rb:100 0.014
Tags: @product
2:20.387
Before features/support/hooks.rb:269 0.023
Given a computer 0.218
And I start Tails from USB drive "old" with network unplugged and I login 1:33.824
Then Tails is running from USB drive "old" 0.316
And I create a persistent partition 34.969
And I take note of which tps features are available 1.675
Then a Tails persistence partition exists on USB drive "old" 0.928
And I shutdown Tails and wait for the computer to power off 8.455
After features/support/hooks.rb:326 0.230
After features/support/hooks.rb:100 0.010
Tags: @product
2:56.552
Before features/support/hooks.rb:269 0.007
Given a computer 0.492
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.271
Then Tails is running from USB drive "old" 0.389
And all tps features are active 1.835
When I write some files expected to persist 2.001
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.234
And all persistence configuration files have safe access rights 0.448
And all persistent directories from the old Tails version have safe access rights 2.473
And I take note of which tps features are available 0.418
And I shutdown Tails and wait for the computer to power off 4.461
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.524
After features/support/hooks.rb:326 0.137
After features/support/hooks.rb:100 0.010
Tags: @product
2:29.479
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.556
And I log in to a new session 19.294
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.930
And I plug USB drive "to_upgrade" 2.425
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.947
Then the running Tails is installed on USB drive "to_upgrade" 20.915
And I unplug USB drive "to_upgrade" 0.205
And I unplug USB drive "__internal" 0.205
After features/support/hooks.rb:326 1.915
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.771
Before features/support/hooks.rb:269 0.005
Given a computer 0.180
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.555
Then all tps features from the old Tails version are active 1.757
And Tails is running from USB drive "to_upgrade" 0.369
And the boot device has safe access rights 3.843
And the expected persistent files created with the old Tails version are present in the filesystem 1.517
And all persistent directories from the old Tails version have safe access rights 2.546
After features/support/hooks.rb:326 0.670
After features/support/hooks.rb:100 0.038
Tags: @product @automatic_upgrade
6:36.276
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 11.853
And no SquashFS delta is installed 0.095
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.358
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.078
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.299
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.489
When the network is plugged 0.086
And Tor is ready 22.362
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.911
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.541
Given I shutdown Tails and wait for the computer to power off 9.009
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.354
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.524
And the file system changes introduced in version 6.2~testoverlayfs are present 0.307
And only the 6.2~testoverlayfs SquashFS delta is installed 0.058
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.400
# 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.272
When the network is plugged 0.085
And Tor is ready 17.300
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.775
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.660
Given I shutdown Tails and wait for the computer to power off 4.523
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.308
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 1.875
And the file system changes introduced in version 6.3~testoverlayfs are present 0.477
And only the 6.3~testoverlayfs SquashFS delta is installed 0.097
# 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.386
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.316
When the network is plugged 0.064
And Tor is ready 18.996
Then the Upgrader considers the system as up-to-date 0.361
# 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.847
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.166
After features/support/hooks.rb:326 0.748
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
38.014
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.624
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.467
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.083
And the signing key used by the Upgrader is outdated 0.840
But a current signing key is available on our website 0.000
When the network is plugged 0.072
And Tor is ready 19.484
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.441
After features/support/hooks.rb:326 0.741
After features/support/hooks.rb:100 0.000