Project Number Date
test_Tails_ISO_devel 4623 17 Sep 2026, 11:19

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:20.060 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.795
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given a computer 0.078
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 14.425
When I start Tails from USB drive "old" with network unplugged 45.447
Then the boot device has safe access rights 2.246
And Tails is running from USB drive "old" 0.206
And there is no persistence partition on USB drive "old" 0.027
And process "udev-watchdog" is running 0.038
And udev-watchdog is monitoring the correct device 0.173
And I unplug USB drive "old" 0.110
After features/support/hooks.rb:339 1.226
After features/support/hooks.rb:108 0.005
Tags: @product
1:24.391
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.107
And I start Tails from USB drive "old" with network unplugged and I login 47.596
Then Tails is running from USB drive "old" 0.207
And I create a persistent partition 24.752
And I take note of which tps features are available 7.263
Then a Tails persistence partition exists on USB drive "old" 0.467
And I shutdown Tails and wait for the computer to power off 3.996
After features/support/hooks.rb:339 0.450
After features/support/hooks.rb:108 0.005
Tags: @product
1:37.246
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.126
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.606
Then Tails is running from USB drive "old" 0.182
And all tps features are active 8.497
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.162
And all persistence configuration files have safe access rights 0.255
And all persistent directories from the old Tails version have safe access rights 1.774
And I take note of which tps features are available 6.953
And I shutdown Tails and wait for the computer to power off 4.153
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 11.421
After features/support/hooks.rb:339 0.568
After features/support/hooks.rb:108 0.008
Tags: @product
2:14.857
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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.853
And I log in to a new session 12.461
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.857
And I plug USB drive "to_upgrade" 2.179
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.261
Then the running Tails is installed on USB drive "to_upgrade" 18.972
And I unplug USB drive "to_upgrade" 0.127
And I unplug USB drive "__internal" 0.144
After features/support/hooks.rb:339 1.831
After features/support/hooks.rb:108 0.000
Tags: @product
1:8.331
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.082
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.214
Then all tps features from the old Tails version are active 0.928
And Tails is running from USB drive "to_upgrade" 0.195
And the boot device has safe access rights 2.196
And the expected persistent files created with the old Tails version are present in the filesystem 0.973
And all persistent directories from the old Tails version have safe access rights 1.740
After features/support/hooks.rb:339 0.896
After features/support/hooks.rb:108 0.008
Tags: @product @automatic_upgrade
3:31.423
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.300
And no SquashFS delta is installed 0.072
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.359
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.203
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.319
When the network is plugged 0.048
And Tor is ready 11.733
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.594
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.058
Given I shutdown Tails and wait for the computer to power off 5.254
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.611
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 8.453
And the file system changes introduced in version 6.2~testoverlayfs are present 0.231
And only the 6.2~testoverlayfs SquashFS delta is installed 0.046
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.138
# 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.193
When the network is plugged 0.025
And Tor is ready 11.682
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.329
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.097
Given I shutdown Tails and wait for the computer to power off 4.143
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.290
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 7.692
And the file system changes introduced in version 6.3~testoverlayfs are present 0.396
And only the 6.3~testoverlayfs SquashFS delta is installed 0.074
# 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.170
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.179
When the network is plugged 0.029
And Tor is ready 11.026
Then the Upgrader considers the system as up-to-date 0.105
# 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.165
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.342
After features/support/hooks.rb:339 0.984
After features/support/hooks.rb:108 0.049
Tags: @product @automatic_upgrade
20.015
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.936
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.314
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the signing key used by the Upgrader is outdated 0.054
But a current signing key is available on our website 0.000
When the network is plugged 0.032
And Tor is ready 9.734
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.900
After features/support/hooks.rb:339 0.642
After features/support/hooks.rb:108 0.000