Project Number Date
test_Tails_ISO_stable 6502 13 Jul 2026, 20:23

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 12:32.618 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:11.012
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.102
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 14.260
When I start Tails from USB drive "old" with network unplugged 51.835
Then the boot device has safe access rights 3.053
And Tails is running from USB drive "old" 0.252
And there is no persistence partition on USB drive "old" 0.042
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.161
After features/support/hooks.rb:339 3.589
After features/support/hooks.rb:108 0.006
Tags: @product
1:36.632
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.064
And I start Tails from USB drive "old" with network unplugged and I login 56.484
Then Tails is running from USB drive "old" 0.252
And I create a persistent partition 26.437
And I take note of which tps features are available 4.473
Then a Tails persistence partition exists on USB drive "old" 0.632
And I shutdown Tails and wait for the computer to power off 8.287
After features/support/hooks.rb:339 0.331
After features/support/hooks.rb:108 0.018
Tags: @product
1:44.929
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.061
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:8.784
Then Tails is running from USB drive "old" 0.254
And all tps features are active 6.242
When I write some files expected to persist 1.527
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.194
And all persistence configuration files have safe access rights 0.405
And all persistent directories from the old Tails version have safe access rights 2.408
And I take note of which tps features are available 3.977
And I shutdown Tails and wait for the computer to power off 8.181
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 12.891
After features/support/hooks.rb:339 0.447
After features/support/hooks.rb:108 0.008
Tags: @product
2:13.257
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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 8.524
And I log in to a new session 12.643
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.876
And I plug USB drive "to_upgrade" 2.205
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.187
Then the running Tails is installed on USB drive "to_upgrade" 16.511
And I unplug USB drive "to_upgrade" 0.127
And I unplug USB drive "__internal" 0.180
After features/support/hooks.rb:339 2.294
After features/support/hooks.rb:108 0.000
Tags: @product
1:17.258
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.066
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.935
Then all tps features from the old Tails version are active 1.496
And Tails is running from USB drive "to_upgrade" 0.316
And the boot device has safe access rights 2.907
And the expected persistent files created with the old Tails version are present in the filesystem 1.288
And all persistent directories from the old Tails version have safe access rights 2.246
After features/support/hooks.rb:339 0.576
After features/support/hooks.rb:108 0.016
Tags: @product @automatic_upgrade
4:8.474
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.496
And no SquashFS delta is installed 0.083
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.276
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.325
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.401
When the network is plugged 0.014
And Tor is ready 12.390
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.547
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.309
Given I shutdown Tails and wait for the computer to power off 11.555
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.307
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 5.783
And the file system changes introduced in version 6.2~testoverlayfs are present 0.299
And only the 6.2~testoverlayfs SquashFS delta is installed 0.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.160
# 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.231
When the network is plugged 0.016
And Tor is ready 10.960
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.217
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.772
Given I shutdown Tails and wait for the computer to power off 8.000
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.416
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 5.168
And the file system changes introduced in version 6.3~testoverlayfs are present 0.315
And only the 6.3~testoverlayfs SquashFS delta is installed 0.056
# 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.138
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.215
When the network is plugged 0.015
And Tor is ready 10.354
Then the Upgrader considers the system as up-to-date 10.494
# 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 4.610
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.392
After features/support/hooks.rb:339 0.922
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
21.053
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.974
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.241
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the signing key used by the Upgrader is outdated 0.037
But a current signing key is available on our website 0.000
When the network is plugged 0.023
And Tor is ready 10.182
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.549
After features/support/hooks.rb:339 0.759
After features/support/hooks.rb:108 0.000