Project Number Date
test_Tails_ISO_stable 5182 14 Oct 2024, 12:38

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 20:38.073 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:12.855
Before features/support/hooks.rb:269 0.005
Given a computer 0.200
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 29.308
When I start Tails from USB drive "old" with network unplugged 1:38.175
Then the boot device has safe access rights 3.041
And Tails is running from USB drive "old" 0.343
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.103
And udev-watchdog is monitoring the correct device 0.332
And I unplug USB drive "old" 0.192
After features/support/hooks.rb:326 3.747
After features/support/hooks.rb:100 0.008
Tags: @product
2:7.436
Before features/support/hooks.rb:269 0.005
Given a computer 0.197
And I start Tails from USB drive "old" with network unplugged and I login 1:23.317
Then Tails is running from USB drive "old" 0.310
And I create a persistent partition 34.433
And I take note of which tps features are available 1.388
Then a Tails persistence partition exists on USB drive "old" 0.912
And I shutdown Tails and wait for the computer to power off 6.877
After features/support/hooks.rb:326 0.160
After features/support/hooks.rb:100 0.010
Tags: @product
2:54.124
Before features/support/hooks.rb:269 0.006
Given a computer 0.250
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.218
Then Tails is running from USB drive "old" 0.336
And all tps features are active 2.205
When I write some files expected to persist 1.719
# 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.468
And all persistent directories from the old Tails version have safe access rights 3.215
And I take note of which tps features are available 0.549
And I shutdown Tails and wait for the computer to power off 4.387
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.517
After features/support/hooks.rb:326 0.144
After features/support/hooks.rb:100 0.010
Tags: @product
2:35.078
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.552
And I log in to a new session 20.672
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.900
And I plug USB drive "to_upgrade" 2.372
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.851
Then the running Tails is installed on USB drive "to_upgrade" 23.316
And I unplug USB drive "to_upgrade" 0.200
And I unplug USB drive "__internal" 0.210
After features/support/hooks.rb:326 2.540
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.451
Before features/support/hooks.rb:269 0.005
Given a computer 0.217
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.221
Then all tps features from the old Tails version are active 1.670
And Tails is running from USB drive "to_upgrade" 0.401
And the boot device has safe access rights 3.205
And the expected persistent files created with the old Tails version are present in the filesystem 1.617
And all persistent directories from the old Tails version have safe access rights 3.116
After features/support/hooks.rb:326 0.749
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
7:44.957
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 16.087
And no SquashFS delta is installed 0.571
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.320
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.367
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.465
When the network is plugged 0.064
And Tor is ready 24.554
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.274
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.895
Given I shutdown Tails and wait for the computer to power off 1:25.314
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.892
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 2.461
And the file system changes introduced in version 6.2~testoverlayfs are present 0.355
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.471
# 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.330
When the network is plugged 0.075
And Tor is ready 18.153
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.407
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.329
Given I shutdown Tails and wait for the computer to power off 4.342
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.178
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.092
And the file system changes introduced in version 6.3~testoverlayfs are present 0.557
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.315
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.404
When the network is plugged 0.074
And Tor is ready 17.152
Then the Upgrader considers the system as up-to-date 0.351
# 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.799
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.043
After features/support/hooks.rb:326 0.896
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
42.169
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.559
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.394
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the signing key used by the Upgrader is outdated 1.061
But a current signing key is available on our website 0.000
When the network is plugged 0.088
And Tor is ready 22.011
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.996
After features/support/hooks.rb:326 0.868
After features/support/hooks.rb:100 0.000