Project Number Date
test_Tails_ISO_devel 3874 18 Jun 2025, 16:06

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 32:12.303 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
4:13.378
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.019
Given a computer 0.258
And I create a 7200 MiB disk named "old" 0.054
And I plug USB drive "old" 1.076
And I write an old version of the Tails USB image to disk "old" 56.509
When I start Tails from USB drive "old" with network unplugged 2:58.305
Then the boot device has safe access rights 5.368
And Tails is running from USB drive "old" 0.469
And there is no persistence partition on USB drive "old" 0.084
And process "udev-watchdog" is running 0.131
And udev-watchdog is monitoring the correct device 0.808
And I unplug USB drive "old" 10.312
After features/support/hooks.rb:330 1.141
After features/support/hooks.rb:100 0.017
Tags: @product
3:19.329
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.013
Given a computer 0.301
And I start Tails from USB drive "old" with network unplugged and I login 2:12.755
Then Tails is running from USB drive "old" 1.528
And I create a persistent partition 45.933
And I take note of which tps features are available 2.770
Then a Tails persistence partition exists on USB drive "old" 0.912
And I shutdown Tails and wait for the computer to power off 15.128
After features/support/hooks.rb:330 0.239
After features/support/hooks.rb:100 0.021
Tags: @product
5:39.817
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.022
Given a computer 0.684
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 4:12.633
Then Tails is running from USB drive "old" 4.271
And all tps features are active 3.748
When I write some files expected to persist 2.506
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.530
And all persistence configuration files have safe access rights 0.721
And all persistent directories from the old Tails version have safe access rights 7.699
And I take note of which tps features are available 1.410
And I shutdown Tails and wait for the computer to power off 10.069
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 55.543
After features/support/hooks.rb:330 0.248
After features/support/hooks.rb:100 0.023
Tags: @product
3:47.394
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.013
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 15.453
And I log in to a new session 29.937
And I clone USB drive "old" to a new USB drive "to_upgrade" 4.248
And I plug USB drive "to_upgrade" 9.393
When I upgrade Tails to USB drive "to_upgrade" by cloning 2:13.142
Then the running Tails is installed on USB drive "to_upgrade" 34.722
And I unplug USB drive "to_upgrade" 0.251
And I unplug USB drive "__internal" 0.243
After features/support/hooks.rb:330 5.388
After features/support/hooks.rb:100 0.000
Tags: @product
3:30.925
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.033
Given a computer 0.986
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 3:10.346
Then all tps features from the old Tails version are active 2.360
And Tails is running from USB drive "to_upgrade" 0.453
And the boot device has safe access rights 12.444
And the expected persistent files created with the old Tails version are present in the filesystem 1.569
And all persistent directories from the old Tails version have safe access rights 2.763
After features/support/hooks.rb:330 0.725
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
10:38.965
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 19.838
And no SquashFS delta is installed 0.389
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.563
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.097
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.348
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.769
When the network is plugged 0.145
And Tor is ready 31.484
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.460
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 27.648
Given I shutdown Tails and wait for the computer to power off 12.928
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 3:9.841
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 3.759
And the file system changes introduced in version 6.2~testoverlayfs are present 0.380
And only the 6.2~testoverlayfs SquashFS delta is installed 0.085
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.360
# 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.343
When the network is plugged 0.089
And Tor is ready 55.268
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.766
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 17.846
Given I shutdown Tails and wait for the computer to power off 6.950
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 3:18.244
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 3.216
And the file system changes introduced in version 6.3~testoverlayfs are present 0.991
And only the 6.3~testoverlayfs SquashFS delta is installed 0.095
# 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.493
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.408
When the network is plugged 0.096
And Tor is ready 28.610
Then the Upgrader considers the system as up-to-date 0.467
# 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 24.897
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.043
After features/support/hooks.rb:330 1.044
After features/support/hooks.rb:100 0.101
Tags: @product @automatic_upgrade
1:2.492
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.070
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 19.818
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.642
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.092
And the signing key used by the Upgrader is outdated 0.071
But a current signing key is available on our website 0.000
When the network is plugged 0.103
And Tor is ready 32.687
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.075
After features/support/hooks.rb:330 1.385
After features/support/hooks.rb:100 0.000