Project Number Date
test_Tails_ISO_devel 4434 06 Jun 2026, 11:12

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:26.782 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:5.010
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.054
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 13.393
When I start Tails from USB drive "old" with network unplugged 47.217
Then the boot device has safe access rights 2.617
And Tails is running from USB drive "old" 0.230
And there is no persistence partition on USB drive "old" 0.051
And process "udev-watchdog" is running 0.069
And udev-watchdog is monitoring the correct device 0.210
And I unplug USB drive "old" 0.144
After features/support/hooks.rb:335 3.553
After features/support/hooks.rb:104 0.008
Tags: @product
1:29.083
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.058
And I start Tails from USB drive "old" with network unplugged and I login 54.661
Then Tails is running from USB drive "old" 0.254
And I create a persistent partition 25.287
And I take note of which tps features are available 0.340
Then a Tails persistence partition exists on USB drive "old" 0.472
And I shutdown Tails and wait for the computer to power off 8.008
After features/support/hooks.rb:335 0.332
After features/support/hooks.rb:104 0.019
Tags: @product
1:28.014
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.009
Given a computer 0.146
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.632
Then Tails is running from USB drive "old" 0.247
And all tps features are active 1.134
When I write some files expected to persist 1.251
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.196
And all persistence configuration files have safe access rights 0.310
And all persistent directories from the old Tails version have safe access rights 1.824
And I take note of which tps features are available 0.230
And I shutdown Tails and wait for the computer to power off 8.049
# 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.990
After features/support/hooks.rb:335 0.391
After features/support/hooks.rb:104 0.007
Tags: @product
2:12.779
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 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.427
And I log in to a new session 13.402
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.692
And I plug USB drive "to_upgrade" 2.256
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.753
Then the running Tails is installed on USB drive "to_upgrade" 15.977
And I unplug USB drive "to_upgrade" 0.137
And I unplug USB drive "__internal" 0.132
After features/support/hooks.rb:335 2.065
After features/support/hooks.rb:104 0.000
Tags: @product
1:9.360
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.052
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.180
Then all tps features from the old Tails version are active 0.979
And Tails is running from USB drive "to_upgrade" 0.220
And the boot device has safe access rights 2.624
And the expected persistent files created with the old Tails version are present in the filesystem 1.065
And all persistent directories from the old Tails version have safe access rights 2.236
After features/support/hooks.rb:335 1.043
After features/support/hooks.rb:104 0.006
Tags: @product @automatic_upgrade
3:41.340
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.459
And no SquashFS delta is installed 0.054
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.248
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.245
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.358
When the network is plugged 0.014
And Tor is ready 12.657
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.529
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.031
Given I shutdown Tails and wait for the computer to power off 5.393
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.562
Then Tails is running version 6.2~testoverlayfs 0.009
And all tps features are active 1.208
And the file system changes introduced in version 6.2~testoverlayfs are present 0.282
And only the 6.2~testoverlayfs SquashFS delta is installed 0.050
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.167
# 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.179
When the network is plugged 0.015
And Tor is ready 9.949
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.927
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.976
Given I shutdown Tails and wait for the computer to power off 8.349
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.722
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.051
And the file system changes introduced in version 6.3~testoverlayfs are present 0.471
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.144
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.218
When the network is plugged 0.016
And Tor is ready 11.541
Then the Upgrader considers the system as up-to-date 10.614
# 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.350
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.438
After features/support/hooks.rb:335 1.127
After features/support/hooks.rb:104 0.012
Tags: @product @automatic_upgrade
21.192
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.558
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.216
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the signing key used by the Upgrader is outdated 0.045
But a current signing key is available on our website 0.000
When the network is plugged 0.024
And Tor is ready 10.671
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.637
After features/support/hooks.rb:335 1.101
After features/support/hooks.rb:104 0.000