Project Number Date
test_Tails_ISO_stable 4834 08 May 2024, 21:21

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:29.914 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:19.714
Before features/support/hooks.rb:259 0.003
Given a computer 1.060
And I create a 7200 MiB disk named "old" 0.679
And I plug USB drive "old" 1.190
And I write an old version of the Tails USB image to disk "old" 30.394
When I start Tails from USB drive "old" with network unplugged 1:42.206
Then the boot device has safe access rights 3.226
And Tails is running from USB drive "old" 0.304
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.088
And udev-watchdog is monitoring the correct device 0.300
And I unplug USB drive "old" 0.194
After features/support/hooks.rb:305 3.644
After features/support/hooks.rb:89 0.050
Tags: @product
2:12.166
Before features/support/hooks.rb:259 0.006
Given a computer 0.205
And I start Tails from USB drive "old" with network unplugged and I login 1:24.497
Then Tails is running from USB drive "old" 0.328
And I create a persistent partition 36.538
And I take note of which tps features are available 1.344
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.421
After features/support/hooks.rb:305 0.144
After features/support/hooks.rb:89 0.007
Tags: @product
2:54.628
Before features/support/hooks.rb:259 0.004
Given a computer 0.188
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.703
Then Tails is running from USB drive "old" 0.393
And all tps features are active 2.328
When I write some files expected to persist 1.955
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.398
And all persistence configuration files have safe access rights 1.518
And all persistent directories from the old Tails version have safe access rights 2.738
And I take note of which tps features are available 0.498
And I shutdown Tails and wait for the computer to power off 4.532
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.371
After features/support/hooks.rb:305 0.110
After features/support/hooks.rb:89 0.008
Tags: @product
2:32.034
Before features/support/hooks.rb:259 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 10.533
And I log in to a new session 19.223
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.602
And I plug USB drive "to_upgrade" 2.439
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.372
Then the running Tails is installed on USB drive "to_upgrade" 22.443
And I unplug USB drive "to_upgrade" 0.223
And I unplug USB drive "__internal" 0.196
After features/support/hooks.rb:305 2.950
After features/support/hooks.rb:89 0.000
Tags: @product
2:18.737
Before features/support/hooks.rb:259 0.004
Given a computer 0.225
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.456
Then all tps features from the old Tails version are active 1.915
And Tails is running from USB drive "to_upgrade" 0.336
And the boot device has safe access rights 3.682
And the expected persistent files created with the old Tails version are present in the filesystem 1.595
And all persistent directories from the old Tails version have safe access rights 2.525
After features/support/hooks.rb:305 0.704
After features/support/hooks.rb:89 0.016
Tags: @product @automatic_upgrade
6:37.056
Before features/support/hooks.rb:259 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.076
And no SquashFS delta is installed 0.105
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.469
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.333
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.435
When the network is plugged 0.103
And Tor is ready 20.645
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.386
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.049
Given I shutdown Tails and wait for the computer to power off 9.070
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.641
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.493
And the file system changes introduced in version 6.2~testoverlayfs are present 0.341
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.360
# 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.047
And Tor is ready 18.816
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.446
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.779
Given I shutdown Tails and wait for the computer to power off 4.608
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.195
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.155
And the file system changes introduced in version 6.3~testoverlayfs are present 0.587
And only the 6.3~testoverlayfs SquashFS delta is installed 0.080
# 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.334
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.278
When the network is plugged 0.039
And Tor is ready 17.105
Then the Upgrader considers the system as up-to-date 10.831
# 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 16.824
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.957
After features/support/hooks.rb:305 0.759
After features/support/hooks.rb:89 0.017
Tags: @product @automatic_upgrade
35.576
Before features/support/hooks.rb:259 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.468
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.557
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.665
But a current signing key is available on our website 0.000
When the network is plugged 0.057
And Tor is ready 17.528
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.214
After features/support/hooks.rb:305 1.687
After features/support/hooks.rb:89 0.000