Project Number Date
test_Tails_ISO_20263-test-suite-disable-spice-vdagent 18 23 Mar 2025, 16:22

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:54.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:13.013
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.175
And I create a 7200 MiB disk named "old" 0.037
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 30.560
When I start Tails from USB drive "old" with network unplugged 1:36.939
Then the boot device has safe access rights 3.260
And Tails is running from USB drive "old" 0.317
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.102
And udev-watchdog is monitoring the correct device 0.297
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:330 7.157
After features/support/hooks.rb:100 0.009
Tags: @product
2:16.610
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.180
And I start Tails from USB drive "old" with network unplugged and I login 1:34.446
Then Tails is running from USB drive "old" 0.323
And I create a persistent partition 31.212
And I take note of which tps features are available 1.412
Then a Tails persistence partition exists on USB drive "old" 0.764
And I shutdown Tails and wait for the computer to power off 8.270
After features/support/hooks.rb:330 0.196
After features/support/hooks.rb:100 0.009
Tags: @product
3:4.089
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.176
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:24.779
Then Tails is running from USB drive "old" 1.874
And all tps features are active 2.060
When I write some files expected to persist 3.270
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.207
And all persistence configuration files have safe access rights 0.337
And all persistent directories from the old Tails version have safe access rights 2.328
And I take note of which tps features are available 0.432
And I shutdown Tails and wait for the computer to power off 4.675
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.946
After features/support/hooks.rb:330 0.108
After features/support/hooks.rb:100 0.013
Tags: @product
2:26.361
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 9.670
And I log in to a new session 18.822
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.761
And I plug USB drive "to_upgrade" 2.487
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.366
Then the running Tails is installed on USB drive "to_upgrade" 19.851
And I unplug USB drive "to_upgrade" 0.199
And I unplug USB drive "__internal" 0.201
After features/support/hooks.rb:330 1.918
After features/support/hooks.rb:100 0.000
Tags: @product
2:25.036
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.184
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:15.752
Then all tps features from the old Tails version are active 1.596
And Tails is running from USB drive "to_upgrade" 0.306
And the boot device has safe access rights 3.231
And the expected persistent files created with the old Tails version are present in the filesystem 1.527
And all persistent directories from the old Tails version have safe access rights 2.436
After features/support/hooks.rb:330 0.884
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:55.050
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 10.781
And no SquashFS delta is installed 0.110
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.299
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.289
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.532
When the network is plugged 0.068
And Tor is ready 21.518
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.416
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.461
Given I shutdown Tails and wait for the computer to power off 8.387
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:18.746
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.015
And the file system changes introduced in version 6.2~testoverlayfs are present 0.297
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.255
# 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.396
When the network is plugged 0.057
And Tor is ready 16.538
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.418
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.482
Given I shutdown Tails and wait for the computer to power off 57.614
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:17.755
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.905
And the file system changes introduced in version 6.3~testoverlayfs are present 0.580
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.287
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.287
When the network is plugged 0.064
And Tor is ready 17.680
Then the Upgrader considers the system as up-to-date 10.772
# 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 14.837
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.957
After features/support/hooks.rb:330 0.825
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
34.013
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 9.577
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.420
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the signing key used by the Upgrader is outdated 0.059
But a current signing key is available on our website 0.000
When the network is plugged 0.065
And Tor is ready 17.427
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.413
After features/support/hooks.rb:330 0.678
After features/support/hooks.rb:100 0.000