Project Number Date
test_Tails_ISO_devel 3396 21 May 2024, 13:28

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:7.614 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:27.500
Before features/support/hooks.rb:259 0.009
Given a computer 0.207
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 48.838
When I start Tails from USB drive "old" with network unplugged 1:33.431
Then the boot device has safe access rights 2.939
And Tails is running from USB drive "old" 0.307
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.121
And udev-watchdog is monitoring the correct device 0.305
And I unplug USB drive "old" 0.174
After features/support/hooks.rb:305 3.739
After features/support/hooks.rb:89 0.011
Tags: @product
2:14.389
Before features/support/hooks.rb:259 0.007
Given a computer 0.238
And I start Tails from USB drive "old" with network unplugged and I login 1:26.459
Then Tails is running from USB drive "old" 0.343
And I create a persistent partition 36.290
And I take note of which tps features are available 1.504
Then a Tails persistence partition exists on USB drive "old" 0.900
And I shutdown Tails and wait for the computer to power off 8.652
After features/support/hooks.rb:305 0.196
After features/support/hooks.rb:89 0.010
Tags: @product
2:58.711
Before features/support/hooks.rb:259 0.006
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.172
Then Tails is running from USB drive "old" 0.394
And all tps features are active 2.910
When I write some files expected to persist 2.244
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.311
And all persistence configuration files have safe access rights 0.451
And all persistent directories from the old Tails version have safe access rights 3.062
And I take note of which tps features are available 1.887
And I shutdown Tails and wait for the computer to power off 4.689
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.392
After features/support/hooks.rb:305 0.169
After features/support/hooks.rb:89 0.012
Tags: @product
2:27.177
Before features/support/hooks.rb:259 0.010
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.748
And I log in to a new session 18.703
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.392
And I plug USB drive "to_upgrade" 2.430
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.845
Then the running Tails is installed on USB drive "to_upgrade" 16.681
And I unplug USB drive "to_upgrade" 0.194
And I unplug USB drive "__internal" 0.179
After features/support/hooks.rb:305 3.581
After features/support/hooks.rb:89 0.000
Tags: @product
2:27.023
Before features/support/hooks.rb:259 0.010
Given a computer 0.226
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:16.290
Then all tps features from the old Tails version are active 1.809
And Tails is running from USB drive "to_upgrade" 0.344
And the boot device has safe access rights 4.334
And the expected persistent files created with the old Tails version are present in the filesystem 1.581
And all persistent directories from the old Tails version have safe access rights 2.435
After features/support/hooks.rb:305 0.711
After features/support/hooks.rb:89 0.013
Tags: @product @automatic_upgrade
6:57.242
Before features/support/hooks.rb:259 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.147
And no SquashFS delta is installed 0.280
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.428
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.079
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.288
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.470
When the network is plugged 0.045
And Tor is ready 20.401
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.159
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.416
Given I shutdown Tails and wait for the computer to power off 11.199
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.793
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.328
And the file system changes introduced in version 6.2~testoverlayfs are present 0.306
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.441
# 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.298
When the network is plugged 0.051
And Tor is ready 47.892
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.583
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.767
Given I shutdown Tails and wait for the computer to power off 4.568
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.604
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.252
And the file system changes introduced in version 6.3~testoverlayfs are present 0.533
And only the 6.3~testoverlayfs SquashFS delta is installed 0.084
# 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.379
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.310
When the network is plugged 0.055
And Tor is ready 17.274
Then the Upgrader considers the system as up-to-date 0.304
# 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 15.456
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.940
After features/support/hooks.rb:305 0.735
After features/support/hooks.rb:89 0.030
Tags: @product @automatic_upgrade
35.568
Before features/support/hooks.rb:259 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.008
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.441
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 0.467
But a current signing key is available on our website 0.000
When the network is plugged 0.077
And Tor is ready 15.977
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.535
After features/support/hooks.rb:305 1.199
After features/support/hooks.rb:89 0.000