Project Number Date
test_Tails_ISO_devel 3714 02 Mar 2025, 12:43

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 20:18.176 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:12.985
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.190
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 29.935
When I start Tails from USB drive "old" with network unplugged 1:37.714
Then the boot device has safe access rights 3.032
And Tails is running from USB drive "old" 0.352
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.082
And udev-watchdog is monitoring the correct device 0.316
And I unplug USB drive "old" 0.189
After features/support/hooks.rb:330 6.957
After features/support/hooks.rb:100 0.009
Tags: @product
2:22.931
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.221
And I start Tails from USB drive "old" with network unplugged and I login 1:34.287
Then Tails is running from USB drive "old" 0.304
And I create a persistent partition 35.271
And I take note of which tps features are available 1.681
Then a Tails persistence partition exists on USB drive "old" 0.806
And I shutdown Tails and wait for the computer to power off 10.358
After features/support/hooks.rb:330 0.260
After features/support/hooks.rb:100 0.009
Tags: @product
2:59.801
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.213
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.939
Then Tails is running from USB drive "old" 0.345
And all tps features are active 2.392
When I write some files expected to persist 3.381
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.302
And all persistence configuration files have safe access rights 0.396
And all persistent directories from the old Tails version have safe access rights 2.507
And I take note of which tps features are available 0.480
And I shutdown Tails and wait for the computer to power off 6.555
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.286
After features/support/hooks.rb:330 0.124
After features/support/hooks.rb:100 0.007
Tags: @product
2:34.083
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 without a persistent partition and stopped at Tails Greeter's login screen 12.557
And I log in to a new session 23.156
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.501
And I plug USB drive "to_upgrade" 2.448
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.595
Then the running Tails is installed on USB drive "to_upgrade" 20.346
And I unplug USB drive "to_upgrade" 0.254
And I unplug USB drive "__internal" 0.224
After features/support/hooks.rb:330 3.006
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.740
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.210
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.954
Then all tps features from the old Tails version are active 1.804
And Tails is running from USB drive "to_upgrade" 0.317
And the boot device has safe access rights 3.484
And the expected persistent files created with the old Tails version are present in the filesystem 1.460
And all persistent directories from the old Tails version have safe access rights 2.508
After features/support/hooks.rb:330 1.066
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
7:11.528
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.819
And no SquashFS delta is installed 0.094
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.444
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.098
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.469
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.573
When the network is plugged 0.093
And Tor is ready 51.663
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.573
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.911
Given I shutdown Tails and wait for the computer to power off 11.079
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.539
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.338
And the file system changes introduced in version 6.2~testoverlayfs are present 0.312
And only the 6.2~testoverlayfs SquashFS delta is installed 0.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.339
# 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.383
When the network is plugged 0.077
And Tor is ready 18.229
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.524
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.529
Given I shutdown Tails and wait for the computer to power off 4.231
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:16.024
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.206
And the file system changes introduced in version 6.3~testoverlayfs are present 0.514
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.305
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.279
When the network is plugged 0.064
And Tor is ready 17.959
Then the Upgrader considers the system as up-to-date 0.321
# 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.366
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.993
After features/support/hooks.rb:330 0.817
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
40.105
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.444
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.578
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.098
But a current signing key is available on our website 0.000
When the network is plugged 0.111
And Tor is ready 21.263
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.553
After features/support/hooks.rb:330 1.950
After features/support/hooks.rb:100 0.000