Project Number Date
test_Tails_ISO_stable 6503 14 Jul 2026, 08:02

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:52.774 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:2.638
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.052
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.476
When I start Tails from USB drive "old" with network unplugged 44.733
Then the boot device has safe access rights 2.650
And Tails is running from USB drive "old" 0.269
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.059
And udev-watchdog is monitoring the correct device 0.196
And I unplug USB drive "old" 0.131
After features/support/hooks.rb:339 1.375
After features/support/hooks.rb:108 0.006
Tags: @product
1:32.093
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.046
And I start Tails from USB drive "old" with network unplugged and I login 53.934
Then Tails is running from USB drive "old" 0.226
And I create a persistent partition 24.953
And I take note of which tps features are available 4.062
Then a Tails persistence partition exists on USB drive "old" 0.527
And I shutdown Tails and wait for the computer to power off 8.342
After features/support/hooks.rb:339 0.320
After features/support/hooks.rb:108 0.006
Tags: @product
1:38.742
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.048
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.494
Then Tails is running from USB drive "old" 0.236
And all tps features are active 4.889
When I write some files expected to persist 1.324
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.180
And all persistence configuration files have safe access rights 0.317
And all persistent directories from the old Tails version have safe access rights 2.113
And I take note of which tps features are available 4.101
And I shutdown Tails and wait for the computer to power off 7.981
# 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" 12.053
After features/support/hooks.rb:339 0.145
After features/support/hooks.rb:108 0.006
Tags: @product
2:10.477
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.192
And I log in to a new session 13.033
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.949
And I plug USB drive "to_upgrade" 2.218
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.327
Then the running Tails is installed on USB drive "to_upgrade" 14.485
And I unplug USB drive "to_upgrade" 0.148
And I unplug USB drive "__internal" 0.123
After features/support/hooks.rb:339 1.990
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.914
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.051
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.160
Then all tps features from the old Tails version are active 1.000
And Tails is running from USB drive "to_upgrade" 0.264
And the boot device has safe access rights 2.408
And the expected persistent files created with the old Tails version are present in the filesystem 1.062
And all persistent directories from the old Tails version have safe access rights 1.967
After features/support/hooks.rb:339 0.845
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:57.248
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.848
And no SquashFS delta is installed 0.054
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.227
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.201
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.373
When the network is plugged 0.020
And Tor is ready 17.257
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.034
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.405
Given I shutdown Tails and wait for the computer to power off 9.420
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.163
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 4.910
And the file system changes introduced in version 6.2~testoverlayfs are present 0.237
And only the 6.2~testoverlayfs SquashFS delta is installed 0.053
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.153
# 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.195
When the network is plugged 0.015
And Tor is ready 9.587
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.932
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.793
Given I shutdown Tails and wait for the computer to power off 8.127
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.250
Then Tails is running version 6.3~testoverlayfs 0.009
And all tps features are active 4.453
And the file system changes introduced in version 6.3~testoverlayfs are present 0.327
And only the 6.3~testoverlayfs SquashFS delta is installed 0.038
# 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.130
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.198
When the network is plugged 0.018
And Tor is ready 15.763
Then the Upgrader considers the system as up-to-date 10.508
# 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.143
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.336
After features/support/hooks.rb:339 0.713
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
20.658
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.376
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.194
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.033
And the signing key used by the Upgrader is outdated 0.041
But a current signing key is available on our website 0.000
When the network is plugged 0.013
And Tor is ready 9.741
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.258
After features/support/hooks.rb:339 0.550
After features/support/hooks.rb:108 0.000