Project Number Date
test_Tails_ISO_devel 4208 04 Feb 2026, 08:15

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:11.436 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:16.224
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.051
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 14.461
When I start Tails from USB drive "old" with network unplugged 56.613
Then the boot device has safe access rights 3.358
And Tails is running from USB drive "old" 0.263
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.045
And udev-watchdog is monitoring the correct device 0.226
And I unplug USB drive "old" 0.139
After features/support/hooks.rb:331 1.303
After features/support/hooks.rb:100 0.007
Tags: @product
1:24.484
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.058
And I start Tails from USB drive "old" with network unplugged and I login 54.117
Then Tails is running from USB drive "old" 0.276
And I create a persistent partition 24.575
And I take note of which tps features are available 0.812
Then a Tails persistence partition exists on USB drive "old" 0.595
And I shutdown Tails and wait for the computer to power off 4.048
After features/support/hooks.rb:331 0.393
After features/support/hooks.rb:100 0.006
Tags: @product
1:26.264
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.057
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.251
Then Tails is running from USB drive "old" 0.261
And all tps features are active 1.037
When I write some files expected to persist 1.379
# 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.342
And all persistent directories from the old Tails version have safe access rights 2.064
And I take note of which tps features are available 0.166
And I shutdown Tails and wait for the computer to power off 7.064
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.446
After features/support/hooks.rb:331 0.093
After features/support/hooks.rb:100 0.008
Tags: @product
2:22.556
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.124
And I log in to a new session 13.618
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.193
And I plug USB drive "to_upgrade" 2.397
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.971
Then the running Tails is installed on USB drive "to_upgrade" 16.789
And I unplug USB drive "to_upgrade" 0.175
And I unplug USB drive "__internal" 0.285
After features/support/hooks.rb:331 6.734
After features/support/hooks.rb:100 0.000
Tags: @product
1:17.196
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.062
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:9.455
Then all tps features from the old Tails version are active 1.034
And Tails is running from USB drive "to_upgrade" 0.221
And the boot device has safe access rights 2.944
And the expected persistent files created with the old Tails version are present in the filesystem 1.205
And all persistent directories from the old Tails version have safe access rights 2.272
After features/support/hooks.rb:331 0.637
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
4:3.035
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 8.342
And no SquashFS delta is installed 0.071
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.252
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.307
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.432
When the network is plugged 0.013
And Tor is ready 13.186
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.853
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.667
Given I shutdown Tails and wait for the computer to power off 11.812
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.297
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.278
And the file system changes introduced in version 6.2~testoverlayfs are present 0.259
And only the 6.2~testoverlayfs SquashFS delta is installed 0.044
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.147
# 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.234
When the network is plugged 0.015
And Tor is ready 9.978
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.330
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.036
Given I shutdown Tails and wait for the computer to power off 8.099
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.199
Then Tails is running version 6.3~testoverlayfs 0.020
And all tps features are active 1.223
And the file system changes introduced in version 6.3~testoverlayfs are present 0.361
And only the 6.3~testoverlayfs SquashFS delta is installed 0.052
# 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.147
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.213
When the network is plugged 0.060
And Tor is ready 10.830
Then the Upgrader considers the system as up-to-date 10.544
# 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.258
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.413
After features/support/hooks.rb:331 1.046
After features/support/hooks.rb:100 0.029
Tags: @product @automatic_upgrade
21.674
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 7.569
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.043
And the signing key used by the Upgrader is outdated 0.040
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 10.612
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.153
After features/support/hooks.rb:331 0.526
After features/support/hooks.rb:100 0.000