Project Number Date
test_Tails_ISO_20522-ocr-more 51 03 Feb 2025, 05:05

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:54.678 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:6.692
Before features/support/hooks.rb:269 0.005
Given a computer 0.235
And I create a 7200 MiB disk named "old" 0.063
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 28.921
When I start Tails from USB drive "old" with network unplugged 1:32.225
Then the boot device has safe access rights 3.162
And Tails is running from USB drive "old" 0.317
And there is no persistence partition on USB drive "old" 0.081
And process "udev-watchdog" is running 0.108
And udev-watchdog is monitoring the correct device 0.333
And I unplug USB drive "old" 0.188
After features/support/hooks.rb:326 7.222
After features/support/hooks.rb:100 0.008
Tags: @product
2:7.569
Before features/support/hooks.rb:269 0.004
Given a computer 0.237
And I start Tails from USB drive "old" with network unplugged and I login 1:21.607
Then Tails is running from USB drive "old" 0.349
And I create a persistent partition 34.807
And I take note of which tps features are available 1.354
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.401
After features/support/hooks.rb:326 0.144
After features/support/hooks.rb:100 0.007
Tags: @product
2:59.090
Before features/support/hooks.rb:269 0.005
Given a computer 0.299
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.984
Then Tails is running from USB drive "old" 0.386
And all tps features are active 2.245
When I write some files expected to persist 1.628
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.236
And all persistence configuration files have safe access rights 0.380
And all persistent directories from the old Tails version have safe access rights 2.307
And I take note of which tps features are available 0.413
And I shutdown Tails and wait for the computer to power off 4.269
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.938
After features/support/hooks.rb:326 0.107
After features/support/hooks.rb:100 0.008
Tags: @product
2:26.068
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.318
And I log in to a new session 17.981
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.476
And I plug USB drive "to_upgrade" 2.370
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.057
Then the running Tails is installed on USB drive "to_upgrade" 19.425
And I unplug USB drive "to_upgrade" 0.232
And I unplug USB drive "__internal" 0.205
After features/support/hooks.rb:326 4.923
After features/support/hooks.rb:100 0.000
Tags: @product
2:11.379
Before features/support/hooks.rb:269 0.005
Given a computer 0.249
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.630
Then all tps features from the old Tails version are active 2.112
And Tails is running from USB drive "to_upgrade" 0.483
And the boot device has safe access rights 3.045
And the expected persistent files created with the old Tails version are present in the filesystem 1.446
And all persistent directories from the old Tails version have safe access rights 2.410
After features/support/hooks.rb:326 0.878
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:22.787
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.233
And no SquashFS delta is installed 0.515
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.298
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.279
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.467
When the network is plugged 0.076
And Tor is ready 24.649
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.981
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.243
Given I shutdown Tails and wait for the computer to power off 10.554
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.774
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.023
And the file system changes introduced in version 6.2~testoverlayfs are present 0.275
And only the 6.2~testoverlayfs SquashFS delta is installed 0.102
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.337
# 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.244
When the network is plugged 0.070
And Tor is ready 16.589
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.394
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.622
Given I shutdown Tails and wait for the computer to power off 4.318
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.767
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.075
And the file system changes introduced in version 6.3~testoverlayfs are present 0.478
And only the 6.3~testoverlayfs SquashFS delta is installed 0.095
# 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.446
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.403
When the network is plugged 0.292
And Tor is ready 20.123
Then the Upgrader considers the system as up-to-date 0.310
# 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.653
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.999
After features/support/hooks.rb:326 0.768
After features/support/hooks.rb:100 0.041
Tags: @product @automatic_upgrade
41.091
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.195
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.379
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.273
And the signing key used by the Upgrader is outdated 0.081
But a current signing key is available on our website 0.000
When the network is plugged 0.121
And Tor is ready 21.564
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.474
After features/support/hooks.rb:326 0.696
After features/support/hooks.rb:100 0.000