Project Number Date
test_Tails_ISO_devel 4349 17 Apr 2026, 11:17

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:3.881 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.921
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.054
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.596
When I start Tails from USB drive "old" with network unplugged 59.314
Then the boot device has safe access rights 3.206
And Tails is running from USB drive "old" 0.239
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.049
And udev-watchdog is monitoring the correct device 0.200
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:331 1.415
After features/support/hooks.rb:100 0.007
Tags: @product
1:29.938
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.063
And I start Tails from USB drive "old" with network unplugged and I login 55.031
Then Tails is running from USB drive "old" 0.293
And I create a persistent partition 24.775
And I take note of which tps features are available 0.829
Then a Tails persistence partition exists on USB drive "old" 0.544
And I shutdown Tails and wait for the computer to power off 8.399
After features/support/hooks.rb:331 0.485
After features/support/hooks.rb:100 0.007
Tags: @product
1:27.445
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.072
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.304
Then Tails is running from USB drive "old" 0.239
And all tps features are active 1.166
When I write some files expected to persist 1.608
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.200
And all persistence configuration files have safe access rights 0.490
And all persistent directories from the old Tails version have safe access rights 1.874
And I take note of which tps features are available 0.240
And I shutdown Tails and wait for the computer to power off 4.284
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.961
After features/support/hooks.rb:331 0.393
After features/support/hooks.rb:100 0.008
Tags: @product
2:17.530
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.166
And I log in to a new session 17.307
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.098
And I plug USB drive "to_upgrade" 2.297
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.069
Then the running Tails is installed on USB drive "to_upgrade" 16.301
And I unplug USB drive "to_upgrade" 0.141
And I unplug USB drive "__internal" 0.147
After features/support/hooks.rb:331 1.060
After features/support/hooks.rb:100 0.000
Tags: @product
1:10.621
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.065
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.332
Then all tps features from the old Tails version are active 1.037
And Tails is running from USB drive "to_upgrade" 0.282
And the boot device has safe access rights 2.709
And the expected persistent files created with the old Tails version are present in the filesystem 1.185
And all persistent directories from the old Tails version have safe access rights 2.008
After features/support/hooks.rb:331 0.583
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
4:52.170
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.418
And no SquashFS delta is installed 0.080
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.423
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.076
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.264
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.399
When the network is plugged 0.041
And Tor is ready 25.168
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.383
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.084
Given I shutdown Tails and wait for the computer to power off 22.113
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.403
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.073
And the file system changes introduced in version 6.2~testoverlayfs are present 0.233
And only the 6.2~testoverlayfs SquashFS delta is installed 0.049
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.165
# 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.208
When the network is plugged 0.021
And Tor is ready 22.177
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.411
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.916
Given I shutdown Tails and wait for the computer to power off 17.424
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.251
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.228
And the file system changes introduced in version 6.3~testoverlayfs are present 0.366
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.139
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.187
When the network is plugged 0.018
And Tor is ready 21.855
Then the Upgrader considers the system as up-to-date 0.127
# 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.859
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.529
After features/support/hooks.rb:331 0.834
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
28.253
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.096
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.244
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.052
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 19.415
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.371
After features/support/hooks.rb:331 0.921
After features/support/hooks.rb:100 0.000