Project Number Date
test_Tails_ISO_stable 6252 01 Apr 2026, 11:14

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:43.318 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:24.486
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.068
And I create a 7200 MiB disk named "old" 0.015
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 15.606
When I start Tails from USB drive "old" with network unplugged 1:3.631
Then the boot device has safe access rights 3.231
And Tails is running from USB drive "old" 0.307
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.060
And udev-watchdog is monitoring the correct device 0.274
And I unplug USB drive "old" 0.164
After features/support/hooks.rb:331 1.639
After features/support/hooks.rb:100 0.008
Tags: @product
1:36.590
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.074
And I start Tails from USB drive "old" with network unplugged and I login 1:1.276
Then Tails is running from USB drive "old" 0.277
And I create a persistent partition 28.807
And I take note of which tps features are available 1.105
Then a Tails persistence partition exists on USB drive "old" 0.649
And I shutdown Tails and wait for the computer to power off 4.398
After features/support/hooks.rb:331 0.389
After features/support/hooks.rb:100 0.024
Tags: @product
1:33.852
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.020
Given a computer 0.092
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:8.536
Then Tails is running from USB drive "old" 0.522
And all tps features are active 1.317
When I write some files expected to persist 1.923
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.262
And all persistence configuration files have safe access rights 0.597
And all persistent directories from the old Tails version have safe access rights 2.433
And I take note of which tps features are available 0.166
And I shutdown Tails and wait for the computer to power off 4.246
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.754
After features/support/hooks.rb:331 0.526
After features/support/hooks.rb:100 0.009
Tags: @product
2:21.104
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.015
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.975
And I log in to a new session 15.620
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.977
And I plug USB drive "to_upgrade" 2.237
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.699
Then the running Tails is installed on USB drive "to_upgrade" 19.274
And I unplug USB drive "to_upgrade" 0.160
And I unplug USB drive "__internal" 0.158
After features/support/hooks.rb:331 2.551
After features/support/hooks.rb:100 0.000
Tags: @product
1:19.030
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.069
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:10.169
Then all tps features from the old Tails version are active 1.135
And Tails is running from USB drive "to_upgrade" 0.302
And the boot device has safe access rights 3.265
And the expected persistent files created with the old Tails version are present in the filesystem 1.560
And all persistent directories from the old Tails version have safe access rights 2.526
After features/support/hooks.rb:331 0.808
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
4:59.753
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.045
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.870
And no SquashFS delta is installed 0.101
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.341
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.265
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.456
When the network is plugged 0.016
And Tor is ready 22.974
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.566
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.868
Given I shutdown Tails and wait for the computer to power off 19.751
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:20.560
Then Tails is running version 6.2~testoverlayfs 0.021
And all tps features are active 1.238
And the file system changes introduced in version 6.2~testoverlayfs are present 0.298
And only the 6.2~testoverlayfs SquashFS delta is installed 0.054
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.157
# 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.236
When the network is plugged 0.018
And Tor is ready 22.565
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.390
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.628
Given I shutdown Tails and wait for the computer to power off 18.144
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.817
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.451
And the file system changes introduced in version 6.3~testoverlayfs are present 0.373
And only the 6.3~testoverlayfs SquashFS delta is installed 0.066
# 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.153
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.285
When the network is plugged 0.021
And Tor is ready 22.562
Then the Upgrader considers the system as up-to-date 0.177
# 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.629
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.632
After features/support/hooks.rb:331 0.913
After features/support/hooks.rb:100 0.025
Tags: @product @automatic_upgrade
28.500
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.448
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.261
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.075
And the signing key used by the Upgrader is outdated 0.084
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 19.208
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.401
After features/support/hooks.rb:331 0.927
After features/support/hooks.rb:100 0.000