Project Number Date
test_Tails_ISO_20522-ocr-more 46 30 Jan 2025, 16:01

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.870 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.596
Before features/support/hooks.rb:269 0.004
Given a computer 0.204
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 31.677
When I start Tails from USB drive "old" with network unplugged 1:29.403
Then the boot device has safe access rights 3.189
And Tails is running from USB drive "old" 0.304
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.106
And udev-watchdog is monitoring the correct device 0.343
And I unplug USB drive "old" 0.204
After features/support/hooks.rb:326 3.577
After features/support/hooks.rb:100 0.009
Tags: @product
2:13.312
Before features/support/hooks.rb:269 0.005
Given a computer 0.223
And I start Tails from USB drive "old" with network unplugged and I login 1:26.705
Then Tails is running from USB drive "old" 0.376
And I create a persistent partition 35.175
And I take note of which tps features are available 1.553
Then a Tails persistence partition exists on USB drive "old" 0.852
And I shutdown Tails and wait for the computer to power off 8.424
After features/support/hooks.rb:326 0.132
After features/support/hooks.rb:100 0.008
Tags: @product
2:55.132
Before features/support/hooks.rb:269 0.005
Given a computer 0.233
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.878
Then Tails is running from USB drive "old" 0.421
And all tps features are active 2.076
When I write some files expected to persist 1.922
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.419
And all persistence configuration files have safe access rights 0.668
And all persistent directories from the old Tails version have safe access rights 2.710
And I take note of which tps features are available 0.521
And I shutdown Tails and wait for the computer to power off 4.225
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.052
After features/support/hooks.rb:326 0.183
After features/support/hooks.rb:100 0.008
Tags: @product
2:25.557
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 11.127
And I log in to a new session 19.290
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.564
And I plug USB drive "to_upgrade" 2.450
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.441
Then the running Tails is installed on USB drive "to_upgrade" 17.226
And I unplug USB drive "to_upgrade" 0.218
And I unplug USB drive "__internal" 0.237
After features/support/hooks.rb:326 2.938
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.676
Before features/support/hooks.rb:269 0.005
Given a computer 0.231
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.508
Then all tps features from the old Tails version are active 1.681
And Tails is running from USB drive "to_upgrade" 0.326
And the boot device has safe access rights 3.339
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 2.825
After features/support/hooks.rb:326 0.948
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:52.776
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 30.347
And no SquashFS delta is installed 0.253
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.334
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.286
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.482
When the network is plugged 0.083
And Tor is ready 19.983
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.708
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.114
Given I shutdown Tails and wait for the computer to power off 12.402
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.018
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.289
And the file system changes introduced in version 6.2~testoverlayfs are present 0.344
And only the 6.2~testoverlayfs SquashFS delta is installed 0.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.320
# 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.243
When the network is plugged 0.080
And Tor is ready 17.710
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.533
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.266
Given I shutdown Tails and wait for the computer to power off 4.303
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.881
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.673
And the file system changes introduced in version 6.3~testoverlayfs are present 0.532
And only the 6.3~testoverlayfs SquashFS delta is installed 0.077
# 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.309
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.280
When the network is plugged 0.082
And Tor is ready 18.997
Then the Upgrader considers the system as up-to-date 0.319
# 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.332
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.016
After features/support/hooks.rb:326 0.688
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
48.819
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 23.063
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.357
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the signing key used by the Upgrader is outdated 0.085
But a current signing key is available on our website 0.000
When the network is plugged 0.093
And Tor is ready 18.250
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.895
After features/support/hooks.rb:326 0.668
After features/support/hooks.rb:100 0.000