Project Number Date
test_Tails_ISO_devel 4100 04 Dec 2025, 19:20

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 16:32.933 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
1:49.251
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.214
And I create a 7200 MiB disk named "old" 0.058
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 32.081
When I start Tails from USB drive "old" with network unplugged 1:11.612
Then the boot device has safe access rights 3.317
And Tails is running from USB drive "old" 0.353
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.068
And udev-watchdog is monitoring the correct device 0.242
And I unplug USB drive "old" 0.186
After features/support/hooks.rb:331 3.523
After features/support/hooks.rb:100 0.009
Tags: @product
1:58.149
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login 1:23.544
Then Tails is running from USB drive "old" 0.337
And I create a persistent partition 29.047
And I take note of which tps features are available 1.221
Then a Tails persistence partition exists on USB drive "old" 0.682
And I shutdown Tails and wait for the computer to power off 3.118
After features/support/hooks.rb:331 0.553
After features/support/hooks.rb:100 0.074
Tags: @product
2:9.316
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.014
Given a computer 0.307
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:35.458
Then Tails is running from USB drive "old" 0.310
And all tps features are active 1.796
When I write some files expected to persist 1.664
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.384
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.362
And I take note of which tps features are available 0.508
And I shutdown Tails and wait for the computer to power off 7.719
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.399
After features/support/hooks.rb:331 0.180
After features/support/hooks.rb:100 0.011
Tags: @product
3:0.044
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 without a persistent partition and stopped at Tails Greeter's login screen 11.707
And I log in to a new session 15.639
And I clone USB drive "old" to a new USB drive "to_upgrade" 7.942
And I plug USB drive "to_upgrade" 2.354
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:58.149
Then the running Tails is installed on USB drive "to_upgrade" 23.743
And I unplug USB drive "to_upgrade" 0.203
And I unplug USB drive "__internal" 0.304
After features/support/hooks.rb:331 7.764
After features/support/hooks.rb:100 0.000
Tags: @product
2:2.888
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 7.338
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:42.610
Then all tps features from the old Tails version are active 1.967
And Tails is running from USB drive "to_upgrade" 0.316
And the boot device has safe access rights 6.031
And the expected persistent files created with the old Tails version are present in the filesystem 2.468
And all persistent directories from the old Tails version have safe access rights 2.156
After features/support/hooks.rb:331 2.376
After features/support/hooks.rb:100 0.265
Tags: @product @automatic_upgrade
4:58.974
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.263
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.641
And no SquashFS delta is installed 0.086
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.285
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.291
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.452
When the network is plugged 0.079
And Tor is ready 14.271
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.716
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 15.887
Given I shutdown Tails and wait for the computer to power off 20.750
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:29.160
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.689
And the file system changes introduced in version 6.2~testoverlayfs are present 0.339
And only the 6.2~testoverlayfs SquashFS delta is installed 0.063
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.150
# 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.248
When the network is plugged 0.053
And Tor is ready 12.310
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.661
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.815
Given I shutdown Tails and wait for the computer to power off 7.834
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:20.906
Then Tails is running version 6.3~testoverlayfs 0.634
And all tps features are active 6.525
And the file system changes introduced in version 6.3~testoverlayfs are present 0.554
And only the 6.3~testoverlayfs SquashFS delta is installed 0.074
# 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.175
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.256
When the network is plugged 0.055
And Tor is ready 13.207
Then the Upgrader considers the system as up-to-date 0.141
# 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 7.008
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.570
After features/support/hooks.rb:331 0.984
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
34.308
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.933
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.280
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.085
And the signing key used by the Upgrader is outdated 0.063
But a current signing key is available on our website 0.000
When the network is plugged 9.396
And Tor is ready 12.943
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.604
After features/support/hooks.rb:331 1.209
After features/support/hooks.rb:100 0.000