Project Number Date
test_Tails_ISO_devel 4283 16 Mar 2026, 11:25

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:13.396 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:17.154
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.090
And I create a 7200 MiB disk named "old" 0.012
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 14.384
When I start Tails from USB drive "old" with network unplugged 58.098
Then the boot device has safe access rights 2.874
And Tails is running from USB drive "old" 0.230
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.044
And udev-watchdog is monitoring the correct device 0.214
And I unplug USB drive "old" 0.137
After features/support/hooks.rb:331 3.462
After features/support/hooks.rb:100 0.007
Tags: @product
1:31.479
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.068
And I start Tails from USB drive "old" with network unplugged and I login 56.053
Then Tails is running from USB drive "old" 0.242
And I create a persistent partition 25.440
And I take note of which tps features are available 0.719
Then a Tails persistence partition exists on USB drive "old" 0.515
And I shutdown Tails and wait for the computer to power off 8.440
After features/support/hooks.rb:331 0.421
After features/support/hooks.rb:100 0.008
Tags: @product
1:30.714
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.059
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.108
Then Tails is running from USB drive "old" 0.279
And all tps features are active 1.119
When I write some files expected to persist 1.402
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.192
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.034
And I take note of which tps features are available 0.260
And I shutdown Tails and wait for the computer to power off 8.229
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.626
After features/support/hooks.rb:331 0.188
After features/support/hooks.rb:100 0.007
Tags: @product
2:17.901
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 8.573
And I log in to a new session 12.796
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.058
And I plug USB drive "to_upgrade" 2.287
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.343
Then the running Tails is installed on USB drive "to_upgrade" 18.532
And I unplug USB drive "to_upgrade" 0.166
And I unplug USB drive "__internal" 0.144
After features/support/hooks.rb:331 3.487
After features/support/hooks.rb:100 0.000
Tags: @product
1:14.290
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.109
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.916
Then all tps features from the old Tails version are active 0.950
And Tails is running from USB drive "to_upgrade" 0.294
And the boot device has safe access rights 2.773
And the expected persistent files created with the old Tails version are present in the filesystem 1.226
And all persistent directories from the old Tails version have safe access rights 2.019
After features/support/hooks.rb:331 0.961
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
4:54.059
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 8.789
And no SquashFS delta is installed 0.092
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.287
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.339
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.395
When the network is plugged 0.044
And Tor is ready 24.144
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.424
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.036
Given I shutdown Tails and wait for the computer to power off 21.301
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.454
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.227
And the file system changes introduced in version 6.2~testoverlayfs are present 0.230
And only the 6.2~testoverlayfs SquashFS delta is installed 0.048
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.154
# 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.212
When the network is plugged 0.019
And Tor is ready 21.822
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.391
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.795
Given I shutdown Tails and wait for the computer to power off 17.569
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.588
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.411
And the file system changes introduced in version 6.3~testoverlayfs are present 0.408
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.245
When the network is plugged 0.017
And Tor is ready 21.964
Then the Upgrader considers the system as up-to-date 0.115
# 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.776
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.451
After features/support/hooks.rb:331 1.032
After features/support/hooks.rb:100 0.045
Tags: @product @automatic_upgrade
27.795
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 7.596
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.247
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the signing key used by the Upgrader is outdated 0.043
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 19.448
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.402
After features/support/hooks.rb:331 0.970
After features/support/hooks.rb:100 0.000