Project Number Date
test_Tails_ISO_stable 6059 14 Jan 2026, 07:52

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:19.300 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:9.994
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.059
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 14.061
When I start Tails from USB drive "old" with network unplugged 50.905
Then the boot device has safe access rights 3.213
And Tails is running from USB drive "old" 0.273
And there is no persistence partition on USB drive "old" 0.053
And process "udev-watchdog" is running 0.053
And udev-watchdog is monitoring the correct device 0.221
And I unplug USB drive "old" 0.128
After features/support/hooks.rb:331 3.587
After features/support/hooks.rb:100 0.008
Tags: @product
1:28.234
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.050
And I start Tails from USB drive "old" with network unplugged and I login 53.635
Then Tails is running from USB drive "old" 0.512
And I create a persistent partition 24.601
And I take note of which tps features are available 0.872
Then a Tails persistence partition exists on USB drive "old" 0.622
And I shutdown Tails and wait for the computer to power off 7.938
After features/support/hooks.rb:331 0.620
After features/support/hooks.rb:100 0.006
Tags: @product
1:27.168
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.866
Then Tails is running from USB drive "old" 0.310
And all tps features are active 1.190
When I write some files expected to persist 1.266
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.151
And all persistence configuration files have safe access rights 0.294
And all persistent directories from the old Tails version have safe access rights 2.296
And I take note of which tps features are available 0.193
And I shutdown Tails and wait for the computer to power off 8.188
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.358
After features/support/hooks.rb:331 0.192
After features/support/hooks.rb:100 0.006
Tags: @product
2:11.812
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 8.658
And I log in to a new session 10.098
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.959
And I plug USB drive "to_upgrade" 2.209
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.517
Then the running Tails is installed on USB drive "to_upgrade" 16.111
And I unplug USB drive "to_upgrade" 0.129
And I unplug USB drive "__internal" 0.127
After features/support/hooks.rb:331 3.900
After features/support/hooks.rb:100 0.000
Tags: @product
1:12.964
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.078
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.446
Then all tps features from the old Tails version are active 1.110
And Tails is running from USB drive "to_upgrade" 0.279
And the boot device has safe access rights 2.907
And the expected persistent files created with the old Tails version are present in the filesystem 1.214
And all persistent directories from the old Tails version have safe access rights 1.927
After features/support/hooks.rb:331 0.747
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
3:30.673
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.121
And no SquashFS delta is installed 0.064
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.289
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.549
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.430
When the network is plugged 0.015
And Tor is ready 12.280
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.687
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.799
Given I shutdown Tails and wait for the computer to power off 10.099
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.958
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.225
And the file system changes introduced in version 6.2~testoverlayfs are present 0.223
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.144
# 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.197
When the network is plugged 0.018
And Tor is ready 11.762
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.768
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.079
Given I shutdown Tails and wait for the computer to power off 8.268
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.186
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.294
And the file system changes introduced in version 6.3~testoverlayfs are present 0.391
And only the 6.3~testoverlayfs SquashFS delta is installed 0.051
# 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.195
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.193
When the network is plugged 0.018
And Tor is ready 9.926
Then the Upgrader considers the system as up-to-date 0.103
# 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.689
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.483
After features/support/hooks.rb:331 0.805
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
18.452
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 7.655
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.198
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
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.014
And Tor is ready 8.133
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.354
After features/support/hooks.rb:331 0.760
After features/support/hooks.rb:100 0.000