Project Number Date
test_Tails_ISO_devel 4211 04 Feb 2026, 17: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 11:2.900 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.716
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.050
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 12.940
When I start Tails from USB drive "old" with network unplugged 53.707
Then the boot device has safe access rights 2.381
And Tails is running from USB drive "old" 0.214
And there is no persistence partition on USB drive "old" 0.040
And process "udev-watchdog" is running 0.045
And udev-watchdog is monitoring the correct device 0.182
And I unplug USB drive "old" 0.127
After features/support/hooks.rb:331 1.253
After features/support/hooks.rb:100 0.005
Tags: @product
1:24.559
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.047
And I start Tails from USB drive "old" with network unplugged and I login 51.562
Then Tails is running from USB drive "old" 0.263
And I create a persistent partition 23.729
And I take note of which tps features are available 0.636
Then a Tails persistence partition exists on USB drive "old" 0.498
And I shutdown Tails and wait for the computer to power off 7.821
After features/support/hooks.rb:331 0.312
After features/support/hooks.rb:100 0.005
Tags: @product
1:22.368
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.048
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.630
Then Tails is running from USB drive "old" 0.287
And all tps features are active 1.084
When I write some files expected to persist 1.200
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.281
And all persistence configuration files have safe access rights 0.315
And all persistent directories from the old Tails version have safe access rights 1.899
And I take note of which tps features are available 0.147
And I shutdown Tails and wait for the computer to power off 7.957
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.514
After features/support/hooks.rb:331 0.463
After features/support/hooks.rb:100 0.006
Tags: @product
2:8.262
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 without a persistent partition and stopped at Tails Greeter's login screen 8.214
And I log in to a new session 9.054
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.013
And I plug USB drive "to_upgrade" 2.237
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.545
Then the running Tails is installed on USB drive "to_upgrade" 14.924
And I unplug USB drive "to_upgrade" 0.136
And I unplug USB drive "__internal" 0.135
After features/support/hooks.rb:331 1.771
After features/support/hooks.rb:100 0.000
Tags: @product
1:4.751
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.055
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.326
Then all tps features from the old Tails version are active 0.922
And Tails is running from USB drive "to_upgrade" 0.203
And the boot device has safe access rights 2.319
And the expected persistent files created with the old Tails version are present in the filesystem 1.043
And all persistent directories from the old Tails version have safe access rights 1.880
After features/support/hooks.rb:331 0.928
After features/support/hooks.rb:100 0.033
Tags: @product @automatic_upgrade
3:32.123
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.174
And no SquashFS delta is installed 0.053
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.254
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.201
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.341
When the network is plugged 0.014
And Tor is ready 13.146
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.794
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.178
Given I shutdown Tails and wait for the computer to power off 9.213
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.666
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.090
And the file system changes introduced in version 6.2~testoverlayfs are present 0.226
And only the 6.2~testoverlayfs SquashFS delta is installed 0.043
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.113
# 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.203
When the network is plugged 0.015
And Tor is ready 10.896
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.727
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.594
Given I shutdown Tails and wait for the computer to power off 7.903
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.641
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.100
And the file system changes introduced in version 6.3~testoverlayfs are present 0.355
And only the 6.3~testoverlayfs SquashFS delta is installed 0.047
# 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.176
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.179
When the network is plugged 0.015
And Tor is ready 11.047
Then the Upgrader considers the system as up-to-date 10.499
# 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 3.796
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.344
After features/support/hooks.rb:331 0.684
After features/support/hooks.rb:100 0.027
Tags: @product @automatic_upgrade
20.120
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.287
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.194
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the signing key used by the Upgrader is outdated 0.046
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 10.220
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.311
After features/support/hooks.rb:331 0.615
After features/support/hooks.rb:100 0.000