Project Number Date
test_Tails_ISO_devel 4323 06 Apr 2026, 18: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 12:59.918 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.125
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.054
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.023
And I write an old version of the Tails USB image to disk "old" 14.544
When I start Tails from USB drive "old" with network unplugged 57.637
Then the boot device has safe access rights 3.103
And Tails is running from USB drive "old" 0.292
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.055
And udev-watchdog is monitoring the correct device 0.220
And I unplug USB drive "old" 0.143
After features/support/hooks.rb:331 1.561
After features/support/hooks.rb:100 0.006
Tags: @product
1:31.519
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.060
And I start Tails from USB drive "old" with network unplugged and I login 56.683
Then Tails is running from USB drive "old" 0.250
And I create a persistent partition 24.626
And I take note of which tps features are available 0.742
Then a Tails persistence partition exists on USB drive "old" 0.566
And I shutdown Tails and wait for the computer to power off 8.588
After features/support/hooks.rb:331 0.392
After features/support/hooks.rb:100 0.016
Tags: @product
1:31.783
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.095
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.002
Then Tails is running from USB drive "old" 0.321
And all tps features are active 1.326
When I write some files expected to persist 1.519
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.211
And all persistence configuration files have safe access rights 0.501
And all persistent directories from the old Tails version have safe access rights 2.136
And I take note of which tps features are available 0.152
And I shutdown Tails and wait for the computer to power off 8.199
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.317
After features/support/hooks.rb:331 0.522
After features/support/hooks.rb:100 0.008
Tags: @product
2:15.665
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 9.225
And I log in to a new session 13.577
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.000
And I plug USB drive "to_upgrade" 2.289
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.246
Then the running Tails is installed on USB drive "to_upgrade" 17.044
And I unplug USB drive "to_upgrade" 0.143
And I unplug USB drive "__internal" 0.139
After features/support/hooks.rb:331 0.832
After features/support/hooks.rb:100 0.000
Tags: @product
1:15.180
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.062
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.617
Then all tps features from the old Tails version are active 1.080
And Tails is running from USB drive "to_upgrade" 0.273
And the boot device has safe access rights 3.512
And the expected persistent files created with the old Tails version are present in the filesystem 1.602
And all persistent directories from the old Tails version have safe access rights 2.030
After features/support/hooks.rb:331 0.570
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:42.949
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 8.273
And no SquashFS delta is installed 0.072
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.223
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.226
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.353
When the network is plugged 0.013
And Tor is ready 21.339
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.402
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.254
Given I shutdown Tails and wait for the computer to power off 15.340
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.947
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.352
And the file system changes introduced in version 6.2~testoverlayfs are present 0.335
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.155
# 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.242
When the network is plugged 0.029
And Tor is ready 23.173
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.528
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.633
Given I shutdown Tails and wait for the computer to power off 13.683
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.305
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.672
And the file system changes introduced in version 6.3~testoverlayfs are present 0.398
And only the 6.3~testoverlayfs SquashFS delta is installed 0.093
# 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.142
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.234
When the network is plugged 0.021
And Tor is ready 22.967
Then the Upgrader considers the system as up-to-date 0.111
# 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.902
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.399
After features/support/hooks.rb:331 1.081
After features/support/hooks.rb:100 0.059
Tags: @product @automatic_upgrade
25.695
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.432
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.228
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the signing key used by the Upgrader is outdated 0.051
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 17.522
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.394
After features/support/hooks.rb:331 1.096
After features/support/hooks.rb:100 0.000