Project Number Date
test_Tails_ISO_stable 5051 27 Aug 2024, 16:22

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:27.575 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:11.702
Before features/support/hooks.rb:269 0.003
Given a computer 0.170
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 33.150
When I start Tails from USB drive "old" with network unplugged 1:33.147
Then the boot device has safe access rights 3.099
And Tails is running from USB drive "old" 0.330
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.357
And I unplug USB drive "old" 0.183
After features/support/hooks.rb:326 3.727
After features/support/hooks.rb:100 0.008
Tags: @product
2:7.828
Before features/support/hooks.rb:269 0.004
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login 1:24.569
Then Tails is running from USB drive "old" 0.346
And I create a persistent partition 32.022
And I take note of which tps features are available 1.680
Then a Tails persistence partition exists on USB drive "old" 0.822
And I shutdown Tails and wait for the computer to power off 8.185
After features/support/hooks.rb:326 0.182
After features/support/hooks.rb:100 0.009
Tags: @product
2:48.490
Before features/support/hooks.rb:269 0.005
Given a computer 0.182
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.399
Then Tails is running from USB drive "old" 0.303
And all tps features are active 1.946
When I write some files expected to persist 1.575
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.246
And all persistence configuration files have safe access rights 0.369
And all persistent directories from the old Tails version have safe access rights 2.503
And I take note of which tps features are available 0.391
And I shutdown Tails and wait for the computer to power off 4.234
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.338
After features/support/hooks.rb:326 0.102
After features/support/hooks.rb:100 0.009
Tags: @product
2:24.747
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 10.261
And I log in to a new session 18.270
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.866
And I plug USB drive "to_upgrade" 2.464
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.888
Then the running Tails is installed on USB drive "to_upgrade" 18.580
And I unplug USB drive "to_upgrade" 0.190
And I unplug USB drive "__internal" 0.226
After features/support/hooks.rb:326 1.438
After features/support/hooks.rb:100 0.000
Tags: @product
2:10.158
Before features/support/hooks.rb:269 0.006
Given a computer 0.172
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.105
Then all tps features from the old Tails version are active 1.518
And Tails is running from USB drive "to_upgrade" 0.311
And the boot device has safe access rights 3.071
And the expected persistent files created with the old Tails version are present in the filesystem 1.423
And all persistent directories from the old Tails version have safe access rights 2.555
After features/support/hooks.rb:326 1.138
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:10.227
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.040
And no SquashFS delta is installed 0.078
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.275
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.358
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.452
When the network is plugged 0.060
And Tor is ready 21.093
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.372
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.164
Given I shutdown Tails and wait for the computer to power off 8.699
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.349
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 1.965
And the file system changes introduced in version 6.2~testoverlayfs are present 0.383
And only the 6.2~testoverlayfs SquashFS delta is installed 0.084
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.488
# 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.292
When the network is plugged 0.066
And Tor is ready 18.915
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.821
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.949
Given I shutdown Tails and wait for the computer to power off 4.318
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.835
Then Tails is running version 6.3~testoverlayfs 0.020
And all tps features are active 2.066
And the file system changes introduced in version 6.3~testoverlayfs are present 0.501
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.286
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.255
When the network is plugged 0.060
And Tor is ready 14.613
Then the Upgrader considers the system as up-to-date 0.311
# 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.961
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.944
After features/support/hooks.rb:326 0.835
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
34.419
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 9.293
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.321
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the signing key used by the Upgrader is outdated 1.018
But a current signing key is available on our website 0.000
When the network is plugged 0.068
And Tor is ready 18.694
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.959
After features/support/hooks.rb:326 1.791
After features/support/hooks.rb:100 0.000