Project Number Date
test_Tails_ISO_20522-ocr-more 39 24 Jan 2025, 05:20

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:2.411 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:3.899
Before features/support/hooks.rb:269 0.004
Given a computer 0.177
And I create a 7200 MiB disk named "old" 0.040
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 29.285
When I start Tails from USB drive "old" with network unplugged 1:29.366
Then the boot device has safe access rights 3.031
And Tails is running from USB drive "old" 0.327
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.284
And I unplug USB drive "old" 0.179
After features/support/hooks.rb:326 7.137
After features/support/hooks.rb:100 0.007
Tags: @product
2:6.029
Before features/support/hooks.rb:269 0.003
Given a computer 0.178
And I start Tails from USB drive "old" with network unplugged and I login 1:24.304
Then Tails is running from USB drive "old" 0.335
And I create a persistent partition 32.614
And I take note of which tps features are available 1.431
Then a Tails persistence partition exists on USB drive "old" 0.825
And I shutdown Tails and wait for the computer to power off 6.338
After features/support/hooks.rb:326 0.142
After features/support/hooks.rb:100 0.008
Tags: @product
2:52.091
Before features/support/hooks.rb:269 0.005
Given a computer 0.245
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.983
Then Tails is running from USB drive "old" 0.395
And all tps features are active 1.965
When I write some files expected to persist 1.843
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.243
And all persistence configuration files have safe access rights 0.427
And all persistent directories from the old Tails version have safe access rights 2.407
And I take note of which tps features are available 0.563
And I shutdown Tails and wait for the computer to power off 4.336
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.677
After features/support/hooks.rb:326 0.103
After features/support/hooks.rb:100 0.008
Tags: @product
2:26.968
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 10.811
And I log in to a new session 19.428
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.683
And I plug USB drive "to_upgrade" 2.367
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.207
Then the running Tails is installed on USB drive "to_upgrade" 19.056
And I unplug USB drive "to_upgrade" 0.204
And I unplug USB drive "__internal" 0.206
After features/support/hooks.rb:326 2.992
After features/support/hooks.rb:100 0.000
Tags: @product
2:8.884
Before features/support/hooks.rb:269 0.005
Given a computer 0.218
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:59.683
Then all tps features from the old Tails version are active 1.594
And Tails is running from USB drive "to_upgrade" 0.309
And the boot device has safe access rights 3.172
And the expected persistent files created with the old Tails version are present in the filesystem 1.654
And all persistent directories from the old Tails version have safe access rights 2.251
After features/support/hooks.rb:326 0.729
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:50.263
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.922
And no SquashFS delta is installed 0.082
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.273
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.306
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.507
When the network is plugged 0.060
And Tor is ready 23.366
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.346
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.579
Given I shutdown Tails and wait for the computer to power off 10.456
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:50.249
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.119
And the file system changes introduced in version 6.2~testoverlayfs are present 0.282
And only the 6.2~testoverlayfs SquashFS delta is installed 0.061
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.323
# 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.295
When the network is plugged 0.084
And Tor is ready 18.436
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.651
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.731
Given I shutdown Tails and wait for the computer to power off 4.334
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.833
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.203
And the file system changes introduced in version 6.3~testoverlayfs are present 0.576
And only the 6.3~testoverlayfs SquashFS delta is installed 0.059
# 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.293
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.461
When the network is plugged 0.075
And Tor is ready 46.716
Then the Upgrader considers the system as up-to-date 0.287
# 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.262
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.941
After features/support/hooks.rb:326 0.766
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
34.275
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.679
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.446
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.073
And Tor is ready 17.297
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.648
After features/support/hooks.rb:326 0.672
After features/support/hooks.rb:100 0.000