Project Number Date
test_Tails_ISO_20263-test-suite-disable-spice-vdagent 2 07 Mar 2025, 16:34

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 21:7.800 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:28.869
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.262
And I create a 7200 MiB disk named "old" 0.037
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 32.996
When I start Tails from USB drive "old" with network unplugged 1:49.875
Then the boot device has safe access rights 3.586
And Tails is running from USB drive "old" 0.361
And there is no persistence partition on USB drive "old" 0.081
And process "udev-watchdog" is running 0.108
And udev-watchdog is monitoring the correct device 0.311
And I unplug USB drive "old" 0.199
After features/support/hooks.rb:330 7.041
After features/support/hooks.rb:100 0.008
Tags: @product
2:27.207
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.184
And I start Tails from USB drive "old" with network unplugged and I login 1:43.551
Then Tails is running from USB drive "old" 0.349
And I create a persistent partition 32.525
And I take note of which tps features are available 1.476
Then a Tails persistence partition exists on USB drive "old" 0.832
And I shutdown Tails and wait for the computer to power off 8.288
After features/support/hooks.rb:330 0.165
After features/support/hooks.rb:100 0.008
Tags: @product
3:9.709
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:32.142
Then Tails is running from USB drive "old" 0.757
And all tps features are active 2.060
When I write some files expected to persist 1.705
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.251
And all persistence configuration files have safe access rights 0.402
And all persistent directories from the old Tails version have safe access rights 2.773
And I take note of which tps features are available 0.596
And I shutdown Tails and wait for the computer to power off 4.411
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.423
After features/support/hooks.rb:330 0.169
After features/support/hooks.rb:100 0.011
Tags: @product
2:30.271
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 without a persistent partition and stopped at Tails Greeter's login screen 10.751
And I log in to a new session 20.523
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.719
And I plug USB drive "to_upgrade" 2.484
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.619
Then the running Tails is installed on USB drive "to_upgrade" 18.730
And I unplug USB drive "to_upgrade" 0.231
And I unplug USB drive "__internal" 0.209
After features/support/hooks.rb:330 3.549
After features/support/hooks.rb:100 0.000
Tags: @product
2:31.699
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.209
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:21.438
Then all tps features from the old Tails version are active 1.958
And Tails is running from USB drive "to_upgrade" 0.368
And the boot device has safe access rights 3.393
And the expected persistent files created with the old Tails version are present in the filesystem 1.696
And all persistent directories from the old Tails version have safe access rights 2.634
After features/support/hooks.rb:330 1.374
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:21.601
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.463
And no SquashFS delta is installed 0.279
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.282
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.407
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.541
When the network is plugged 0.067
And Tor is ready 17.011
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.844
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.766
Given I shutdown Tails and wait for the computer to power off 8.560
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:29.270
Then Tails is running version 6.2~testoverlayfs 0.022
And all tps features are active 2.409
And the file system changes introduced in version 6.2~testoverlayfs are present 0.316
And only the 6.2~testoverlayfs SquashFS delta is installed 0.082
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.263
# 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.277
When the network is plugged 0.080
And Tor is ready 16.096
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.002
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.086
Given I shutdown Tails and wait for the computer to power off 4.377
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:22.685
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.899
And the file system changes introduced in version 6.3~testoverlayfs are present 0.517
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.281
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.282
When the network is plugged 0.068
And Tor is ready 17.991
Then the Upgrader considers the system as up-to-date 10.849
# 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.246
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.101
After features/support/hooks.rb:330 0.749
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
38.440
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 with a persistent partition enabled and logged in 10.101
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.454
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.083
And the signing key used by the Upgrader is outdated 0.102
But a current signing key is available on our website 0.000
When the network is plugged 0.060
And Tor is ready 20.854
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.782
After features/support/hooks.rb:330 0.915
After features/support/hooks.rb:100 0.000