Project Number Date
test_Tails_ISO_20522-ocr-more 49 01 Feb 2025, 05:16

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:25.371 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:5.020
Before features/support/hooks.rb:269 0.005
Given a computer 0.190
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.982
When I start Tails from USB drive "old" with network unplugged 1:29.573
Then the boot device has safe access rights 3.176
And Tails is running from USB drive "old" 0.335
And there is no persistence partition on USB drive "old" 0.056
And process "udev-watchdog" is running 0.087
And udev-watchdog is monitoring the correct device 0.338
And I unplug USB drive "old" 0.187
After features/support/hooks.rb:326 3.480
After features/support/hooks.rb:100 0.010
Tags: @product
2:3.792
Before features/support/hooks.rb:269 0.005
Given a computer 0.206
And I start Tails from USB drive "old" with network unplugged and I login 1:20.347
Then Tails is running from USB drive "old" 0.315
And I create a persistent partition 32.364
And I take note of which tps features are available 1.521
Then a Tails persistence partition exists on USB drive "old" 0.811
And I shutdown Tails and wait for the computer to power off 8.225
After features/support/hooks.rb:326 0.182
After features/support/hooks.rb:100 0.007
Tags: @product
2:53.278
Before features/support/hooks.rb:269 0.004
Given a computer 0.175
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.380
Then Tails is running from USB drive "old" 0.551
And all tps features are active 1.909
When I write some files expected to persist 2.170
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.282
And all persistence configuration files have safe access rights 0.366
And all persistent directories from the old Tails version have safe access rights 2.394
And I take note of which tps features are available 0.460
And I shutdown Tails and wait for the computer to power off 4.646
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.941
After features/support/hooks.rb:326 0.105
After features/support/hooks.rb:100 0.008
Tags: @product
2:24.995
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.715
And I log in to a new session 17.711
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.727
And I plug USB drive "to_upgrade" 2.410
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.924
Then the running Tails is installed on USB drive "to_upgrade" 15.980
And I unplug USB drive "to_upgrade" 0.238
And I unplug USB drive "__internal" 0.286
After features/support/hooks.rb:326 3.076
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.050
Before features/support/hooks.rb:269 0.007
Given a computer 0.218
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.612
Then all tps features from the old Tails version are active 1.587
And Tails is running from USB drive "to_upgrade" 0.348
And the boot device has safe access rights 3.075
And the expected persistent files created with the old Tails version are present in the filesystem 1.370
And all persistent directories from the old Tails version have safe access rights 2.838
After features/support/hooks.rb:326 0.706
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:10.712
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.949
And no SquashFS delta is installed 0.079
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.315
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.290
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.485
When the network is plugged 0.067
And Tor is ready 18.788
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.822
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.949
Given I shutdown Tails and wait for the computer to power off 8.545
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.055
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.106
And the file system changes introduced in version 6.2~testoverlayfs are present 0.307
And only the 6.2~testoverlayfs SquashFS delta is installed 0.063
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.314
# 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.302
When the network is plugged 0.074
And Tor is ready 19.065
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.526
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.733
Given I shutdown Tails and wait for the computer to power off 6.344
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.587
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.135
And the file system changes introduced in version 6.3~testoverlayfs are present 0.458
And only the 6.3~testoverlayfs SquashFS delta is installed 0.081
# 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.405
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.301
When the network is plugged 0.080
And Tor is ready 18.714
Then the Upgrader considers the system as up-to-date 0.301
# 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.415
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.945
After features/support/hooks.rb:326 0.765
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
34.520
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.647
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.289
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 0.073
But a current signing key is available on our website 0.000
When the network is plugged 0.083
And Tor is ready 16.785
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.585
After features/support/hooks.rb:326 1.278
After features/support/hooks.rb:100 0.000