Project Number Date
test_Tails_ISO_stable 5332 13 Dec 2024, 08:39

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:50.519 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:4.087
Before features/support/hooks.rb:269 0.006
Given a computer 0.213
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" 29.540
When I start Tails from USB drive "old" with network unplugged 1:29.100
Then the boot device has safe access rights 3.034
And Tails is running from USB drive "old" 0.390
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.088
And udev-watchdog is monitoring the correct device 0.331
And I unplug USB drive "old" 0.213
After features/support/hooks.rb:326 6.750
After features/support/hooks.rb:100 0.009
Tags: @product
2:7.165
Before features/support/hooks.rb:269 0.006
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login 1:24.676
Then Tails is running from USB drive "old" 0.333
And I create a persistent partition 31.445
And I take note of which tps features are available 1.385
Then a Tails persistence partition exists on USB drive "old" 0.795
And I shutdown Tails and wait for the computer to power off 8.343
After features/support/hooks.rb:326 0.168
After features/support/hooks.rb:100 0.009
Tags: @product
2:51.450
Before features/support/hooks.rb:269 0.006
Given a computer 0.174
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.521
Then Tails is running from USB drive "old" 0.332
And all tps features are active 2.060
When I write some files expected to persist 1.718
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.225
And all persistence configuration files have safe access rights 0.395
And all persistent directories from the old Tails version have safe access rights 2.464
And I take note of which tps features are available 0.420
And I shutdown Tails and wait for the computer to power off 4.205
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.931
After features/support/hooks.rb:326 0.154
After features/support/hooks.rb:100 0.008
Tags: @product
2:31.781
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.925
And I log in to a new session 19.408
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.778
And I plug USB drive "to_upgrade" 2.362
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.216
Then the running Tails is installed on USB drive "to_upgrade" 22.668
And I unplug USB drive "to_upgrade" 0.220
And I unplug USB drive "__internal" 0.201
After features/support/hooks.rb:326 1.995
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.436
Before features/support/hooks.rb:269 0.005
Given a computer 0.203
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.878
Then all tps features from the old Tails version are active 1.686
And Tails is running from USB drive "to_upgrade" 0.393
And the boot device has safe access rights 3.219
And the expected persistent files created with the old Tails version are present in the filesystem 1.554
And all persistent directories from the old Tails version have safe access rights 2.501
After features/support/hooks.rb:326 0.619
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:23.255
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 11.298
And no SquashFS delta is installed 0.180
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.579
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.297
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.542
When the network is plugged 0.087
And Tor is ready 22.147
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.336
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.654
Given I shutdown Tails and wait for the computer to power off 8.486
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.504
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.331
And the file system changes introduced in version 6.2~testoverlayfs are present 0.265
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.306
# 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.305
When the network is plugged 0.071
And Tor is ready 18.507
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.410
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.894
Given I shutdown Tails and wait for the computer to power off 4.254
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.994
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.116
And the file system changes introduced in version 6.3~testoverlayfs are present 0.495
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.304
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.273
When the network is plugged 0.085
And Tor is ready 18.865
Then the Upgrader considers the system as up-to-date 0.327
# 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.947
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.154
After features/support/hooks.rb:326 0.721
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
37.341
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.903
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.318
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.857
But a current signing key is available on our website 0.000
When the network is plugged 0.070
And Tor is ready 19.652
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.480
After features/support/hooks.rb:326 0.619
After features/support/hooks.rb:100 0.000