Project Number Date
test_Tails_ISO_20263-test-suite-disable-spice-vdagent 12 17 Mar 2025, 17: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 23:16.989 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:47.837
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.213
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 31.062
When I start Tails from USB drive "old" with network unplugged 2:10.973
Then the boot device has safe access rights 3.524
And Tails is running from USB drive "old" 0.309
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.095
And udev-watchdog is monitoring the correct device 0.293
And I unplug USB drive "old" 0.201
After features/support/hooks.rb:330 3.482
After features/support/hooks.rb:100 0.008
Tags: @product
2:27.022
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.196
And I start Tails from USB drive "old" with network unplugged and I login 1:42.358
Then Tails is running from USB drive "old" 0.460
And I create a persistent partition 32.983
And I take note of which tps features are available 1.562
Then a Tails persistence partition exists on USB drive "old" 0.874
And I shutdown Tails and wait for the computer to power off 8.585
After features/support/hooks.rb:330 0.184
After features/support/hooks.rb:100 0.009
Tags: @product
3:34.280
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.209
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:52.640
Then Tails is running from USB drive "old" 0.372
And all tps features are active 2.421
When I write some files expected to persist 1.968
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.291
And all persistence configuration files have safe access rights 0.544
And all persistent directories from the old Tails version have safe access rights 5.184
And I take note of which tps features are available 0.569
And I shutdown Tails and wait for the computer to power off 4.359
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.718
After features/support/hooks.rb:330 0.209
After features/support/hooks.rb:100 0.009
Tags: @product
2:37.545
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.591
And I log in to a new session 22.647
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.415
And I plug USB drive "to_upgrade" 2.522
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.313
Then the running Tails is installed on USB drive "to_upgrade" 25.426
And I unplug USB drive "to_upgrade" 0.333
And I unplug USB drive "__internal" 0.295
After features/support/hooks.rb:330 3.632
After features/support/hooks.rb:100 0.000
Tags: @product
2:37.862
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.200
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:26.627
Then all tps features from the old Tails version are active 1.916
And Tails is running from USB drive "to_upgrade" 0.391
And the boot device has safe access rights 4.260
And the expected persistent files created with the old Tails version are present in the filesystem 1.662
And all persistent directories from the old Tails version have safe access rights 2.804
After features/support/hooks.rb:330 1.583
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
8:33.021
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 12.011
And no SquashFS delta is installed 0.269
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.548
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.303
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.499
When the network is plugged 0.138
And Tor is ready 24.948
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.938
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.332
Given I shutdown Tails and wait for the computer to power off 1:28.341
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:27.663
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.432
And the file system changes introduced in version 6.2~testoverlayfs are present 0.342
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.258
# 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.251
When the network is plugged 0.074
And Tor is ready 20.284
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.632
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.373
Given I shutdown Tails and wait for the computer to power off 4.357
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:20.198
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.459
And the file system changes introduced in version 6.3~testoverlayfs are present 0.542
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.341
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.321
When the network is plugged 0.301
And Tor is ready 19.417
Then the Upgrader considers the system as up-to-date 0.337
# 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 15.694
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.155
After features/support/hooks.rb:330 0.845
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
39.418
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 9.502
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.592
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.125
And the signing key used by the Upgrader is outdated 0.067
But a current signing key is available on our website 0.000
When the network is plugged 0.112
And Tor is ready 23.869
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.146
After features/support/hooks.rb:330 0.756
After features/support/hooks.rb:100 0.000