Project Number Date
test_Tails_ISO_devel 4147 02 Jan 2026, 14:11

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 13:44.285 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:30.258
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.184
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.043
And I write an old version of the Tails USB image to disk "old" 27.851
When I start Tails from USB drive "old" with network unplugged 57.231
Then the boot device has safe access rights 3.038
And Tails is running from USB drive "old" 0.316
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.054
And udev-watchdog is monitoring the correct device 0.224
And I unplug USB drive "old" 0.199
After features/support/hooks.rb:331 4.058
After features/support/hooks.rb:100 0.009
Tags: @product
1:44.878
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.179
And I start Tails from USB drive "old" with network unplugged and I login 1:4.997
Then Tails is running from USB drive "old" 0.375
And I create a persistent partition 29.151
And I take note of which tps features are available 1.254
Then a Tails persistence partition exists on USB drive "old" 0.695
And I shutdown Tails and wait for the computer to power off 8.224
After features/support/hooks.rb:331 0.629
After features/support/hooks.rb:100 0.011
Tags: @product
1:49.509
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.247
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:15.624
Then Tails is running from USB drive "old" 0.565
And all tps features are active 1.946
When I write some files expected to persist 1.618
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.203
And all persistence configuration files have safe access rights 0.411
And all persistent directories from the old Tails version have safe access rights 2.460
And I take note of which tps features are available 0.486
And I shutdown Tails and wait for the computer to power off 7.667
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.277
After features/support/hooks.rb:331 0.452
After features/support/hooks.rb:100 0.008
Tags: @product
2:22.112
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.057
And I log in to a new session 9.459
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.501
And I plug USB drive "to_upgrade" 4.667
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.765
Then the running Tails is installed on USB drive "to_upgrade" 19.199
And I unplug USB drive "to_upgrade" 0.271
And I unplug USB drive "__internal" 0.189
After features/support/hooks.rb:331 3.743
After features/support/hooks.rb:100 0.000
Tags: @product
1:24.324
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.247
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:14.544
Then all tps features from the old Tails version are active 1.662
And Tails is running from USB drive "to_upgrade" 0.295
And the boot device has safe access rights 3.269
And the expected persistent files created with the old Tails version are present in the filesystem 1.805
And all persistent directories from the old Tails version have safe access rights 2.499
After features/support/hooks.rb:331 0.633
After features/support/hooks.rb:100 0.041
Tags: @product @automatic_upgrade
4:29.508
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 10.249
And no SquashFS delta is installed 0.070
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.214
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.238
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.470
When the network is plugged 0.058
And Tor is ready 13.156
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.733
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 15.666
Given I shutdown Tails and wait for the computer to power off 10.231
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:21.529
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 3.433
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.090
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.225
# 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.307
When the network is plugged 0.071
And Tor is ready 12.405
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.623
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.770
Given I shutdown Tails and wait for the computer to power off 5.077
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:22.742
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 2.502
And the file system changes introduced in version 6.3~testoverlayfs are present 0.450
And only the 6.3~testoverlayfs SquashFS delta is installed 0.053
# 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.159
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.279
When the network is plugged 0.046
And Tor is ready 13.425
Then the Upgrader considers the system as up-to-date 0.183
# 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 6.852
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.741
After features/support/hooks.rb:331 1.969
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
23.693
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.858
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.228
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.072
But a current signing key is available on our website 0.000
When the network is plugged 0.063
And Tor is ready 10.425
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.985
After features/support/hooks.rb:331 0.700
After features/support/hooks.rb:100 0.000