Project Number Date
test_Tails_ISO_devel 3703 20 Feb 2025, 12:51

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:15.445 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:11.444
Before features/support/hooks.rb:269 0.006
Given a computer 0.215
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" 32.395
When I start Tails from USB drive "old" with network unplugged 1:33.675
Then the boot device has safe access rights 3.035
And Tails is running from USB drive "old" 0.338
And there is no persistence partition on USB drive "old" 0.083
And process "udev-watchdog" is running 0.100
And udev-watchdog is monitoring the correct device 0.291
And I unplug USB drive "old" 0.211
After features/support/hooks.rb:326 12.879
After features/support/hooks.rb:100 0.009
Tags: @product
2:8.448
Before features/support/hooks.rb:269 0.006
Given a computer 0.206
And I start Tails from USB drive "old" with network unplugged and I login 1:27.503
Then Tails is running from USB drive "old" 0.382
And I create a persistent partition 31.193
And I take note of which tps features are available 1.945
Then a Tails persistence partition exists on USB drive "old" 0.861
And I shutdown Tails and wait for the computer to power off 6.355
After features/support/hooks.rb:326 0.305
After features/support/hooks.rb:100 0.010
Tags: @product
2:59.527
Before features/support/hooks.rb:269 0.006
Given a computer 0.199
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.565
Then Tails is running from USB drive "old" 0.356
And all tps features are active 2.297
When I write some files expected to persist 1.936
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.221
And all persistence configuration files have safe access rights 0.443
And all persistent directories from the old Tails version have safe access rights 2.703
And I take note of which tps features are available 0.468
And I shutdown Tails and wait for the computer to power off 4.391
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.942
After features/support/hooks.rb:326 0.156
After features/support/hooks.rb:100 0.008
Tags: @product
2:33.764
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 19.274
And I log in to a new session 18.231
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.475
And I plug USB drive "to_upgrade" 2.391
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.199
Then the running Tails is installed on USB drive "to_upgrade" 17.710
And I unplug USB drive "to_upgrade" 0.241
And I unplug USB drive "__internal" 0.240
After features/support/hooks.rb:326 2.935
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.102
Before features/support/hooks.rb:269 0.006
Given a computer 0.207
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.216
Then all tps features from the old Tails version are active 1.601
And Tails is running from USB drive "to_upgrade" 0.419
And the boot device has safe access rights 3.372
And the expected persistent files created with the old Tails version are present in the filesystem 1.447
And all persistent directories from the old Tails version have safe access rights 2.836
After features/support/hooks.rb:326 0.821
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
6:21.050
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.783
And no SquashFS delta is installed 0.337
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.336
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.301
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.418
When the network is plugged 0.077
And Tor is ready 21.975
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.408
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.023
Given I shutdown Tails and wait for the computer to power off 10.927
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.664
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.349
And the file system changes introduced in version 6.2~testoverlayfs are present 0.288
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.310
# 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.273
When the network is plugged 0.066
And Tor is ready 17.619
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.582
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.098
Given I shutdown Tails and wait for the computer to power off 4.320
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.648
Then Tails is running version 6.3~testoverlayfs 0.020
And all tps features are active 2.079
And the file system changes introduced in version 6.3~testoverlayfs are present 0.521
And only the 6.3~testoverlayfs SquashFS delta is installed 0.088
# 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.528
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.467
When the network is plugged 0.067
And Tor is ready 19.047
Then the Upgrader considers the system as up-to-date 0.343
# 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.395
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.542
After features/support/hooks.rb:326 0.812
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
37.107
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.395
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.033
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the signing key used by the Upgrader is outdated 0.070
But a current signing key is available on our website 0.000
When the network is plugged 0.074
And Tor is ready 18.750
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.713
After features/support/hooks.rb:326 1.467
After features/support/hooks.rb:100 0.000