Project Number Date
test_Tails_ISO_20522-ocr-more 23 01 Jan 2025, 05:07

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:9.137 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:1.659
Before features/support/hooks.rb:269 0.005
Given a computer 0.177
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 30.198
When I start Tails from USB drive "old" with network unplugged 1:26.243
Then the boot device has safe access rights 2.946
And Tails is running from USB drive "old" 0.294
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.311
And I unplug USB drive "old" 0.235
After features/support/hooks.rb:326 6.933
After features/support/hooks.rb:100 0.007
Tags: @product
2:7.325
Before features/support/hooks.rb:269 0.005
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login 1:23.103
Then Tails is running from USB drive "old" 0.327
And I create a persistent partition 33.091
And I take note of which tps features are available 1.463
Then a Tails persistence partition exists on USB drive "old" 0.844
And I shutdown Tails and wait for the computer to power off 8.305
After features/support/hooks.rb:326 0.140
After features/support/hooks.rb:100 0.008
Tags: @product
2:59.956
Before features/support/hooks.rb:269 0.004
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.396
Then Tails is running from USB drive "old" 1.782
And all tps features are active 2.235
When I write some files expected to persist 3.365
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.212
And all persistence configuration files have safe access rights 0.520
And all persistent directories from the old Tails version have safe access rights 3.694
And I take note of which tps features are available 0.457
And I shutdown Tails and wait for the computer to power off 4.568
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.525
After features/support/hooks.rb:326 0.152
After features/support/hooks.rb:100 0.009
Tags: @product
2:37.060
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 11.414
And I log in to a new session 24.788
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.702
And I plug USB drive "to_upgrade" 2.625
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.013
Then the running Tails is installed on USB drive "to_upgrade" 22.089
And I unplug USB drive "to_upgrade" 0.200
And I unplug USB drive "__internal" 0.225
After features/support/hooks.rb:326 2.644
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.229
Before features/support/hooks.rb:269 0.005
Given a computer 0.251
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.283
Then all tps features from the old Tails version are active 1.690
And Tails is running from USB drive "to_upgrade" 0.317
And the boot device has safe access rights 3.710
And the expected persistent files created with the old Tails version are present in the filesystem 1.521
And all persistent directories from the old Tails version have safe access rights 2.454
After features/support/hooks.rb:326 0.849
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:13.198
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 12.342
And no SquashFS delta is installed 0.080
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.277
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.440
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.428
When the network is plugged 0.073
And Tor is ready 20.500
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.278
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.556
Given I shutdown Tails and wait for the computer to power off 10.568
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.066
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 2.473
And the file system changes introduced in version 6.2~testoverlayfs are present 0.374
And only the 6.2~testoverlayfs SquashFS delta is installed 0.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.348
# 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.359
When the network is plugged 0.076
And Tor is ready 17.593
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.130
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.887
Given I shutdown Tails and wait for the computer to power off 4.277
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.738
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.101
And the file system changes introduced in version 6.3~testoverlayfs are present 0.580
And only the 6.3~testoverlayfs SquashFS delta is installed 0.098
# 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.288
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.245
When the network is plugged 0.084
And Tor is ready 18.460
Then the Upgrader considers the system as up-to-date 0.411
# 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.945
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.931
After features/support/hooks.rb:326 0.762
After features/support/hooks.rb:100 0.030
Tags: @product @automatic_upgrade
56.707
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 10.094
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.427
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.106
And the signing key used by the Upgrader is outdated 0.122
But a current signing key is available on our website 0.000
When the network is plugged 0.084
And Tor is ready 45.289
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.583
After features/support/hooks.rb:326 0.711
After features/support/hooks.rb:100 0.000