Project Number Date
test_Tails_ISO_stable 6087 23 Jan 2026, 07:26

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 11:59.929 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.858
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.114
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.035
And I write an old version of the Tails USB image to disk "old" 14.635
When I start Tails from USB drive "old" with network unplugged 58.342
Then the boot device has safe access rights 2.985
And Tails is running from USB drive "old" 0.239
And there is no persistence partition on USB drive "old" 0.057
And process "udev-watchdog" is running 0.061
And udev-watchdog is monitoring the correct device 0.216
And I unplug USB drive "old" 0.128
After features/support/hooks.rb:331 3.951
After features/support/hooks.rb:100 0.007
Tags: @product
1:30.917
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.054
And I start Tails from USB drive "old" with network unplugged and I login 55.434
Then Tails is running from USB drive "old" 0.287
And I create a persistent partition 25.651
And I take note of which tps features are available 0.830
Then a Tails persistence partition exists on USB drive "old" 0.553
And I shutdown Tails and wait for the computer to power off 8.105
After features/support/hooks.rb:331 0.497
After features/support/hooks.rb:100 0.007
Tags: @product
1:30.195
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.065
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.715
Then Tails is running from USB drive "old" 0.326
And all tps features are active 1.544
When I write some files expected to persist 1.540
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.232
And all persistence configuration files have safe access rights 0.412
And all persistent directories from the old Tails version have safe access rights 2.153
And I take note of which tps features are available 0.158
And I shutdown Tails and wait for the computer to power off 8.261
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.785
After features/support/hooks.rb:331 0.097
After features/support/hooks.rb:100 0.007
Tags: @product
2:13.736
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 without a persistent partition and stopped at Tails Greeter's login screen 8.969
And I log in to a new session 10.551
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.996
And I plug USB drive "to_upgrade" 2.292
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.713
Then the running Tails is installed on USB drive "to_upgrade" 16.945
And I unplug USB drive "to_upgrade" 0.131
And I unplug USB drive "__internal" 0.135
After features/support/hooks.rb:331 0.903
After features/support/hooks.rb:100 0.000
Tags: @product
1:12.504
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.067
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.633
Then all tps features from the old Tails version are active 1.037
And Tails is running from USB drive "to_upgrade" 0.332
And the boot device has safe access rights 2.779
And the expected persistent files created with the old Tails version are present in the filesystem 1.449
And all persistent directories from the old Tails version have safe access rights 2.204
After features/support/hooks.rb:331 0.732
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
3:53.902
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.456
And no SquashFS delta is installed 0.065
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.330
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.251
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.436
When the network is plugged 0.016
And Tor is ready 13.051
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.872
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.334
Given I shutdown Tails and wait for the computer to power off 9.634
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.169
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.396
And the file system changes introduced in version 6.2~testoverlayfs are present 0.295
And only the 6.2~testoverlayfs SquashFS delta is installed 0.056
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.164
# 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.225
When the network is plugged 0.041
And Tor is ready 11.402
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.637
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.010
Given I shutdown Tails and wait for the computer to power off 8.439
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.650
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.379
And the file system changes introduced in version 6.3~testoverlayfs are present 0.397
And only the 6.3~testoverlayfs SquashFS delta is installed 0.053
# 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.158
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.274
When the network is plugged 0.021
And Tor is ready 12.358
Then the Upgrader considers the system as up-to-date 10.742
# 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.953
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.570
After features/support/hooks.rb:331 1.128
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
20.815
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.636
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.245
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.058
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 10.529
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.283
After features/support/hooks.rb:331 1.030
After features/support/hooks.rb:100 0.000