Project Number Date
test_Tails_ISO_devel 4239 18 Feb 2026, 09:22

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:25.930 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:3.208
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.051
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 13.618
When I start Tails from USB drive "old" with network unplugged 45.244
Then the boot device has safe access rights 2.602
And Tails is running from USB drive "old" 0.251
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.049
And udev-watchdog is monitoring the correct device 0.192
And I unplug USB drive "old" 0.133
After features/support/hooks.rb:331 1.239
After features/support/hooks.rb:100 0.005
Tags: @product
1:24.562
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 51.753
Then Tails is running from USB drive "old" 0.295
And I create a persistent partition 23.196
And I take note of which tps features are available 0.676
Then a Tails persistence partition exists on USB drive "old" 0.468
And I shutdown Tails and wait for the computer to power off 8.123
After features/support/hooks.rb:331 0.305
After features/support/hooks.rb:100 0.006
Tags: @product
1:17.269
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.046
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.838
Then Tails is running from USB drive "old" 0.233
And all tps features are active 1.043
When I write some files expected to persist 1.112
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.175
And all persistence configuration files have safe access rights 0.278
And all persistent directories from the old Tails version have safe access rights 1.732
And I take note of which tps features are available 0.151
And I shutdown Tails and wait for the computer to power off 2.678
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.978
After features/support/hooks.rb:331 0.556
After features/support/hooks.rb:100 0.005
Tags: @product
2:12.133
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 7.833
And I log in to a new session 12.038
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.733
And I plug USB drive "to_upgrade" 2.215
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.003
Then the running Tails is installed on USB drive "to_upgrade" 15.025
And I unplug USB drive "to_upgrade" 0.143
And I unplug USB drive "__internal" 0.139
After features/support/hooks.rb:331 4.204
After features/support/hooks.rb:100 0.000
Tags: @product
1:8.592
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.047
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.110
Then all tps features from the old Tails version are active 0.908
And Tails is running from USB drive "to_upgrade" 0.241
And the boot device has safe access rights 2.412
And the expected persistent files created with the old Tails version are present in the filesystem 1.064
And all persistent directories from the old Tails version have safe access rights 1.806
After features/support/hooks.rb:331 0.716
After features/support/hooks.rb:100 0.005
Tags: @product @automatic_upgrade
3:58.792
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 20.854
And no SquashFS delta is installed 0.058
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.246
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.031
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.212
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.349
When the network is plugged 0.018
And Tor is ready 12.420
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.556
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.182
Given I shutdown Tails and wait for the computer to power off 12.945
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.086
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.160
And the file system changes introduced in version 6.2~testoverlayfs are present 0.237
And only the 6.2~testoverlayfs SquashFS delta is installed 0.052
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.171
# 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.226
When the network is plugged 0.016
And Tor is ready 10.658
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.659
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.830
Given I shutdown Tails and wait for the computer to power off 7.982
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.739
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.060
And the file system changes introduced in version 6.3~testoverlayfs are present 0.359
And only the 6.3~testoverlayfs SquashFS delta is installed 0.054
# 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.165
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.198
When the network is plugged 0.020
And Tor is ready 10.663
Then the Upgrader considers the system as up-to-date 10.525
# 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.704
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.329
After features/support/hooks.rb:331 0.710
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
21.372
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.585
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.287
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.048
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 11.499
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.875
After features/support/hooks.rb:331 0.821
After features/support/hooks.rb:100 0.000