Project Number Date
test_Tails_ISO_20912-test-suite-wget-specific-mirror 4 06 May 2025, 13:28

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 24:43.615 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:53.636
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.017
Given a computer 0.347
And I create a 7200 MiB disk named "old" 0.060
And I plug USB drive "old" 1.110
And I write an old version of the Tails USB image to disk "old" 1:3.695
When I start Tails from USB drive "old" with network unplugged 1:43.644
Then the boot device has safe access rights 3.699
And Tails is running from USB drive "old" 0.357
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.310
And I unplug USB drive "old" 0.245
After features/support/hooks.rb:330 10.352
After features/support/hooks.rb:100 0.012
Tags: @product
2:29.933
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.278
And I start Tails from USB drive "old" with network unplugged and I login 1:43.725
Then Tails is running from USB drive "old" 0.333
And I create a persistent partition 34.222
And I take note of which tps features are available 1.986
Then a Tails persistence partition exists on USB drive "old" 0.862
And I shutdown Tails and wait for the computer to power off 8.523
After features/support/hooks.rb:330 0.204
After features/support/hooks.rb:100 0.010
Tags: @product
3:13.100
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.267
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:31.578
Then Tails is running from USB drive "old" 0.397
And all tps features are active 2.975
When I write some files expected to persist 1.989
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.257
And all persistence configuration files have safe access rights 0.475
And all persistent directories from the old Tails version have safe access rights 2.808
And I take note of which tps features are available 0.609
And I shutdown Tails and wait for the computer to power off 6.340
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.399
After features/support/hooks.rb:330 0.133
After features/support/hooks.rb:100 0.012
Tags: @product
3:5.560
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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 23.860
And I log in to a new session 22.174
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.513
And I plug USB drive "to_upgrade" 2.615
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:43.113
Then the running Tails is installed on USB drive "to_upgrade" 30.747
And I unplug USB drive "to_upgrade" 0.260
And I unplug USB drive "__internal" 0.275
After features/support/hooks.rb:330 3.998
After features/support/hooks.rb:100 0.000
Tags: @product
2:37.740
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.768
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:23.945
Then all tps features from the old Tails version are active 3.851
And Tails is running from USB drive "to_upgrade" 0.556
And the boot device has safe access rights 3.734
And the expected persistent files created with the old Tails version are present in the filesystem 1.764
And all persistent directories from the old Tails version have safe access rights 3.118
After features/support/hooks.rb:330 1.977
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
9:37.599
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 26.513
And no SquashFS delta is installed 0.093
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.489
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.165
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.500
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.512
When the network is plugged 0.092
And Tor is ready 20.851
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.442
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 2:24.344
Given I shutdown Tails and wait for the computer to power off 9.311
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:17.763
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.738
And the file system changes introduced in version 6.2~testoverlayfs are present 0.355
And only the 6.2~testoverlayfs SquashFS delta is installed 0.094
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.432
# 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.293
When the network is plugged 0.095
And Tor is ready 24.277
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.108
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.093
Given I shutdown Tails and wait for the computer to power off 6.804
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.033
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.561
And the file system changes introduced in version 6.3~testoverlayfs are present 0.585
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.325
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.422
When the network is plugged 0.098
And Tor is ready 21.632
Then the Upgrader considers the system as up-to-date 0.361
# 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.236
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.875
After features/support/hooks.rb:330 1.589
After features/support/hooks.rb:100 0.041
Tags: @product @automatic_upgrade
46.044
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 16.357
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.468
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.094
And the signing key used by the Upgrader is outdated 0.077
But a current signing key is available on our website 0.000
When the network is plugged 0.138
And Tor is ready 20.394
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.513
After features/support/hooks.rb:330 0.899
After features/support/hooks.rb:100 0.000