Project Number Date
test_Tails_ISO_stable 4892 16 Jun 2024, 12:36

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:20.778 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:0.091
Before features/support/hooks.rb:269 0.005
Given a computer 0.208
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 34.199
When I start Tails from USB drive "old" with network unplugged 1:20.745
Then the boot device has safe access rights 2.895
And Tails is running from USB drive "old" 0.302
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.268
And I unplug USB drive "old" 0.215
After features/support/hooks.rb:320 7.120
After features/support/hooks.rb:100 0.010
Tags: @product
2:6.642
Before features/support/hooks.rb:269 0.007
Given a computer 0.199
And I start Tails from USB drive "old" with network unplugged and I login 1:20.681
Then Tails is running from USB drive "old" 0.397
And I create a persistent partition 34.560
And I take note of which tps features are available 1.759
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.237
After features/support/hooks.rb:320 0.132
After features/support/hooks.rb:100 0.010
Tags: @product
2:47.647
Before features/support/hooks.rb:269 0.009
Given a computer 0.212
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.729
Then Tails is running from USB drive "old" 0.314
And all tps features are active 1.975
When I write some files expected to persist 1.699
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.320
And all persistence configuration files have safe access rights 0.415
And all persistent directories from the old Tails version have safe access rights 2.256
And I take note of which tps features are available 0.374
And I shutdown Tails and wait for the computer to power off 4.339
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.010
After features/support/hooks.rb:320 0.144
After features/support/hooks.rb:100 0.011
Tags: @product
2:26.102
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.217
And I log in to a new session 17.335
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.360
And I plug USB drive "to_upgrade" 2.424
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.354
Then the running Tails is installed on USB drive "to_upgrade" 19.998
And I unplug USB drive "to_upgrade" 0.213
And I unplug USB drive "__internal" 0.199
After features/support/hooks.rb:320 2.029
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.197
Before features/support/hooks.rb:269 0.007
Given a computer 0.277
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.882
Then all tps features from the old Tails version are active 1.476
And Tails is running from USB drive "to_upgrade" 0.320
And the boot device has safe access rights 3.018
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 2.604
After features/support/hooks.rb:320 0.594
After features/support/hooks.rb:100 0.027
Tags: @product @automatic_upgrade
7:8.737
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.340
And no SquashFS delta is installed 0.066
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.281
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.276
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.530
When the network is plugged 0.044
And Tor is ready 16.506
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.720
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.879
Given I shutdown Tails and wait for the computer to power off 1:9.597
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.487
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.045
And the file system changes introduced in version 6.2~testoverlayfs are present 0.287
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.339
# 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.252
When the network is plugged 0.045
And Tor is ready 20.045
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.047
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.296
Given I shutdown Tails and wait for the computer to power off 4.280
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.556
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.074
And the file system changes introduced in version 6.3~testoverlayfs are present 0.483
And only the 6.3~testoverlayfs SquashFS delta is installed 0.059
# 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.299
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.253
When the network is plugged 0.038
And Tor is ready 17.046
Then the Upgrader considers the system as up-to-date 0.302
# 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.267
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.840
After features/support/hooks.rb:320 0.640
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
34.358
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.744
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.310
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the signing key used by the Upgrader is outdated 1.035
But a current signing key is available on our website 0.000
When the network is plugged 0.035
And Tor is ready 16.684
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.493
After features/support/hooks.rb:320 0.648
After features/support/hooks.rb:100 0.000