Project Number Date
test_Tails_ISO_devel 4171 16 Jan 2026, 08:42

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:24.857 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:32.296
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.202
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.041
And I write an old version of the Tails USB image to disk "old" 31.789
When I start Tails from USB drive "old" with network unplugged 55.276
Then the boot device has safe access rights 3.057
And Tails is running from USB drive "old" 0.267
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.047
And udev-watchdog is monitoring the correct device 0.214
And I unplug USB drive "old" 0.270
After features/support/hooks.rb:331 4.004
After features/support/hooks.rb:100 0.009
Tags: @product
1:39.243
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login 1:0.782
Then Tails is running from USB drive "old" 0.345
And I create a persistent partition 28.389
And I take note of which tps features are available 1.162
Then a Tails persistence partition exists on USB drive "old" 0.668
And I shutdown Tails and wait for the computer to power off 7.705
After features/support/hooks.rb:331 0.219
After features/support/hooks.rb:100 0.009
Tags: @product
1:45.194
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.182
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:12.824
Then Tails is running from USB drive "old" 0.279
And all tps features are active 1.750
When I write some files expected to persist 1.513
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.217
And all persistence configuration files have safe access rights 0.446
And all persistent directories from the old Tails version have safe access rights 2.217
And I take note of which tps features are available 0.483
And I shutdown Tails and wait for the computer to power off 7.674
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.604
After features/support/hooks.rb:331 0.207
After features/support/hooks.rb:100 0.009
Tags: @product
2:28.559
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.118
And I log in to a new session 12.599
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.780
And I plug USB drive "to_upgrade" 2.916
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.360
Then the running Tails is installed on USB drive "to_upgrade" 19.418
And I unplug USB drive "to_upgrade" 0.183
And I unplug USB drive "__internal" 0.182
After features/support/hooks.rb:331 3.758
After features/support/hooks.rb:100 0.000
Tags: @product
1:24.796
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.180
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:16.182
Then all tps features from the old Tails version are active 1.374
And Tails is running from USB drive "to_upgrade" 0.266
And the boot device has safe access rights 3.124
And the expected persistent files created with the old Tails version are present in the filesystem 1.390
And all persistent directories from the old Tails version have safe access rights 2.276
After features/support/hooks.rb:331 1.019
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
4:13.264
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.837
And no SquashFS delta is installed 0.084
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.238
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.277
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.474
When the network is plugged 0.056
And Tor is ready 13.737
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.629
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.451
Given I shutdown Tails and wait for the computer to power off 12.676
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.769
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 1.969
And the file system changes introduced in version 6.2~testoverlayfs are present 0.290
And only the 6.2~testoverlayfs SquashFS delta is installed 0.062
# 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.237
When the network is plugged 0.061
And Tor is ready 12.408
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.805
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.331
Given I shutdown Tails and wait for the computer to power off 7.558
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.829
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 2.058
And the file system changes introduced in version 6.3~testoverlayfs are present 0.485
And only the 6.3~testoverlayfs SquashFS delta is installed 0.058
# 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.142
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.230
When the network is plugged 0.086
And Tor is ready 11.207
Then the Upgrader considers the system as up-to-date 0.123
# 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 5.257
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.602
After features/support/hooks.rb:331 0.837
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
21.502
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 with a persistent partition enabled and logged in 9.616
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.267
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.060
But a current signing key is available on our website 0.000
When the network is plugged 0.046
And Tor is ready 10.898
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.559
After features/support/hooks.rb:331 0.805
After features/support/hooks.rb:100 0.000