Project Number Date
test_Tails_ISO_devel 4284 16 Mar 2026, 13:10

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:47.172 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:10.377
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.103
And I create a 7200 MiB disk named "old" 0.011
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 14.390
When I start Tails from USB drive "old" with network unplugged 51.063
Then the boot device has safe access rights 3.032
And Tails is running from USB drive "old" 0.288
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.218
And I unplug USB drive "old" 0.155
After features/support/hooks.rb:331 3.757
After features/support/hooks.rb:100 0.009
Tags: @product
1:32.484
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.078
And I start Tails from USB drive "old" with network unplugged and I login 56.872
Then Tails is running from USB drive "old" 0.270
And I create a persistent partition 25.264
And I take note of which tps features are available 0.748
Then a Tails persistence partition exists on USB drive "old" 0.641
And I shutdown Tails and wait for the computer to power off 8.607
After features/support/hooks.rb:331 0.403
After features/support/hooks.rb:100 0.006
Tags: @product
1:32.421
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.086
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.092
Then Tails is running from USB drive "old" 0.287
And all tps features are active 1.234
When I write some files expected to persist 1.460
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.189
And all persistence configuration files have safe access rights 0.497
And all persistent directories from the old Tails version have safe access rights 2.002
And I take note of which tps features are available 0.192
And I shutdown Tails and wait for the computer to power off 8.483
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.894
After features/support/hooks.rb:331 0.450
After features/support/hooks.rb:100 0.008
Tags: @product
2:14.176
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 8.824
And I log in to a new session 10.227
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.022
And I plug USB drive "to_upgrade" 2.281
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.960
Then the running Tails is installed on USB drive "to_upgrade" 17.555
And I unplug USB drive "to_upgrade" 0.158
And I unplug USB drive "__internal" 0.146
After features/support/hooks.rb:331 2.269
After features/support/hooks.rb:100 0.000
Tags: @product
1:13.288
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.074
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.561
Then all tps features from the old Tails version are active 1.094
And Tails is running from USB drive "to_upgrade" 0.261
And the boot device has safe access rights 2.858
And the expected persistent files created with the old Tails version are present in the filesystem 1.193
And all persistent directories from the old Tails version have safe access rights 2.243
After features/support/hooks.rb:331 1.022
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
4:38.263
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.532
And no SquashFS delta is installed 0.085
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.288
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.291
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.418
When the network is plugged 0.020
And Tor is ready 20.320
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.413
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.224
Given I shutdown Tails and wait for the computer to power off 20.581
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.397
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.229
And the file system changes introduced in version 6.2~testoverlayfs are present 0.276
And only the 6.2~testoverlayfs SquashFS delta is installed 0.047
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.156
# 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.240
When the network is plugged 0.057
And Tor is ready 20.739
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.433
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.403
Given I shutdown Tails and wait for the computer to power off 12.285
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.367
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 1.238
And the file system changes introduced in version 6.3~testoverlayfs are present 0.390
And only the 6.3~testoverlayfs SquashFS delta is installed 0.062
# 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.331
When the network is plugged 0.075
And Tor is ready 20.918
Then the Upgrader considers the system as up-to-date 0.108
# 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.670
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.452
After features/support/hooks.rb:331 0.751
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
26.160
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.344
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.244
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
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.024
And Tor is ready 18.012
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.423
After features/support/hooks.rb:331 0.627
After features/support/hooks.rb:100 0.000