Project Number Date
test_Tails_ISO_20522-ocr-more 22 31 Dec 2024, 05:10

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:14.027 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.089
Before features/support/hooks.rb:269 0.005
Given a computer 0.273
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.056
And I write an old version of the Tails USB image to disk "old" 27.400
When I start Tails from USB drive "old" with network unplugged 1:46.208
Then the boot device has safe access rights 3.098
And Tails is running from USB drive "old" 0.304
And there is no persistence partition on USB drive "old" 0.078
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.315
And I unplug USB drive "old" 0.208
After features/support/hooks.rb:326 7.042
After features/support/hooks.rb:100 0.009
Tags: @product
2:6.324
Before features/support/hooks.rb:269 0.007
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login 1:20.194
Then Tails is running from USB drive "old" 0.356
And I create a persistent partition 34.934
And I take note of which tps features are available 1.496
Then a Tails persistence partition exists on USB drive "old" 0.846
And I shutdown Tails and wait for the computer to power off 8.297
After features/support/hooks.rb:326 0.143
After features/support/hooks.rb:100 0.009
Tags: @product
2:49.278
Before features/support/hooks.rb:269 0.008
Given a computer 0.209
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.363
Then Tails is running from USB drive "old" 0.349
And all tps features are active 2.058
When I write some files expected to persist 2.412
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.214
And all persistence configuration files have safe access rights 0.440
And all persistent directories from the old Tails version have safe access rights 2.479
And I take note of which tps features are available 0.448
And I shutdown Tails and wait for the computer to power off 4.388
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.913
After features/support/hooks.rb:326 0.133
After features/support/hooks.rb:100 0.010
Tags: @product
2:35.972
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 10.765
And I log in to a new session 24.644
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.761
And I plug USB drive "to_upgrade" 4.145
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.107
Then the running Tails is installed on USB drive "to_upgrade" 21.123
And I unplug USB drive "to_upgrade" 0.205
And I unplug USB drive "__internal" 0.220
After features/support/hooks.rb:326 3.614
After features/support/hooks.rb:100 0.000
Tags: @product
2:10.160
Before features/support/hooks.rb:269 0.007
Given a computer 0.205
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:0.255
Then all tps features from the old Tails version are active 1.682
And Tails is running from USB drive "to_upgrade" 0.335
And the boot device has safe access rights 3.557
And the expected persistent files created with the old Tails version are present in the filesystem 1.508
And all persistent directories from the old Tails version have safe access rights 2.616
After features/support/hooks.rb:326 0.974
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
7:36.854
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 12.252
And no SquashFS delta is installed 0.168
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.288
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.114
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.366
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.421
When the network is plugged 0.091
And Tor is ready 22.138
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.090
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.694
Given I shutdown Tails and wait for the computer to power off 1:24.746
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.587
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.332
And the file system changes introduced in version 6.2~testoverlayfs are present 0.348
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.311
# 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.358
When the network is plugged 0.106
And Tor is ready 18.701
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.632
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.923
Given I shutdown Tails and wait for the computer to power off 4.679
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.222
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.120
And the file system changes introduced in version 6.3~testoverlayfs are present 0.483
And only the 6.3~testoverlayfs SquashFS delta is installed 0.060
# 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.281
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.436
When the network is plugged 0.074
And Tor is ready 19.128
Then the Upgrader considers the system as up-to-date 0.295
# 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.187
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.113
After features/support/hooks.rb:326 0.785
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
36.346
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.912
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.422
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the signing key used by the Upgrader is outdated 0.084
But a current signing key is available on our website 0.000
When the network is plugged 0.074
And Tor is ready 19.953
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.850
After features/support/hooks.rb:326 0.716
After features/support/hooks.rb:100 0.000