Project Number Date
test_Tails_ISO_20522-ocr-more 28 06 Jan 2025, 05:06

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:39.045 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:10.098
Before features/support/hooks.rb:269 0.014
Given a computer 0.247
And I create a 7200 MiB disk named "old" 0.074
And I plug USB drive "old" 1.061
And I write an old version of the Tails USB image to disk "old" 29.875
When I start Tails from USB drive "old" with network unplugged 1:34.798
Then the boot device has safe access rights 3.021
And Tails is running from USB drive "old" 0.314
And there is no persistence partition on USB drive "old" 0.060
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.359
And I unplug USB drive "old" 0.187
After features/support/hooks.rb:326 3.673
After features/support/hooks.rb:100 0.008
Tags: @product
2:8.952
Before features/support/hooks.rb:269 0.005
Given a computer 0.178
And I start Tails from USB drive "old" with network unplugged and I login 1:23.326
Then Tails is running from USB drive "old" 0.325
And I create a persistent partition 34.391
And I take note of which tps features are available 1.613
Then a Tails persistence partition exists on USB drive "old" 0.782
And I shutdown Tails and wait for the computer to power off 8.334
After features/support/hooks.rb:326 0.170
After features/support/hooks.rb:100 0.011
Tags: @product
2:51.208
Before features/support/hooks.rb:269 0.005
Given a computer 0.199
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.213
Then Tails is running from USB drive "old" 0.333
And all tps features are active 2.053
When I write some files expected to persist 1.797
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.271
And all persistence configuration files have safe access rights 0.368
And all persistent directories from the old Tails version have safe access rights 2.334
And I take note of which tps features are available 0.430
And I shutdown Tails and wait for the computer to power off 4.157
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.049
After features/support/hooks.rb:326 0.134
After features/support/hooks.rb:100 0.009
Tags: @product
2:40.063
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.445
And I log in to a new session 24.456
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.923
And I plug USB drive "to_upgrade" 3.903
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.551
Then the running Tails is installed on USB drive "to_upgrade" 23.234
And I unplug USB drive "to_upgrade" 0.275
And I unplug USB drive "__internal" 0.272
After features/support/hooks.rb:326 3.556
After features/support/hooks.rb:100 0.000
Tags: @product
2:6.921
Before features/support/hooks.rb:269 0.006
Given a computer 0.199
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:56.497
Then all tps features from the old Tails version are active 1.922
And Tails is running from USB drive "to_upgrade" 0.359
And the boot device has safe access rights 3.795
And the expected persistent files created with the old Tails version are present in the filesystem 1.494
And all persistent directories from the old Tails version have safe access rights 2.652
After features/support/hooks.rb:326 1.127
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:6.025
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.831
And no SquashFS delta is installed 0.097
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.397
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.076
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.338
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.497
When the network is plugged 0.073
And Tor is ready 23.221
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.281
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.747
Given I shutdown Tails and wait for the computer to power off 11.038
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.714
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.527
And the file system changes introduced in version 6.2~testoverlayfs are present 0.299
And only the 6.2~testoverlayfs SquashFS delta is installed 0.288
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.291
# 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.403
When the network is plugged 0.113
And Tor is ready 47.618
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.584
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.883
Given I shutdown Tails and wait for the computer to power off 6.313
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.980
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.193
And the file system changes introduced in version 6.3~testoverlayfs are present 0.476
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.303
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.315
When the network is plugged 0.063
And Tor is ready 16.350
Then the Upgrader considers the system as up-to-date 10.816
# 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.677
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.100
After features/support/hooks.rb:326 0.793
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
35.775
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 10.332
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.474
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.121
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.091
And Tor is ready 17.908
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.724
After features/support/hooks.rb:326 0.725
After features/support/hooks.rb:100 0.000