Project Number Date
test_Tails_ISO_devel 4181 22 Jan 2026, 09:23

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 13:25.166 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:32.178
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.271
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.044
And I write an old version of the Tails USB image to disk "old" 30.800
When I start Tails from USB drive "old" with network unplugged 55.976
Then the boot device has safe access rights 3.169
And Tails is running from USB drive "old" 0.325
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.066
And udev-watchdog is monitoring the correct device 0.247
And I unplug USB drive "old" 0.164
After features/support/hooks.rb:331 3.534
After features/support/hooks.rb:100 0.009
Tags: @product
1:31.190
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login 59.682
Then Tails is running from USB drive "old" 0.336
And I create a persistent partition 26.121
And I take note of which tps features are available 1.054
Then a Tails persistence partition exists on USB drive "old" 0.649
And I shutdown Tails and wait for the computer to power off 3.158
After features/support/hooks.rb:331 0.219
After features/support/hooks.rb:100 0.010
Tags: @product
1:37.185
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.165
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:10.030
Then Tails is running from USB drive "old" 0.286
And all tps features are active 1.774
When I write some files expected to persist 1.400
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.195
And all persistence configuration files have safe access rights 0.338
And all persistent directories from the old Tails version have safe access rights 2.062
And I take note of which tps features are available 0.490
And I shutdown Tails and wait for the computer to power off 3.104
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.338
After features/support/hooks.rb:331 0.171
After features/support/hooks.rb:100 0.009
Tags: @product
2:26.658
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.114
And I log in to a new session 11.973
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.345
And I plug USB drive "to_upgrade" 2.688
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.347
Then the running Tails is installed on USB drive "to_upgrade" 19.783
And I unplug USB drive "to_upgrade" 0.196
And I unplug USB drive "__internal" 0.208
After features/support/hooks.rb:331 3.858
After features/support/hooks.rb:100 0.000
Tags: @product
1:19.657
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.185
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:11.500
Then all tps features from the old Tails version are active 1.336
And Tails is running from USB drive "to_upgrade" 0.291
And the boot device has safe access rights 2.908
And the expected persistent files created with the old Tails version are present in the filesystem 1.198
And all persistent directories from the old Tails version have safe access rights 2.236
After features/support/hooks.rb:331 0.724
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
4:35.560
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.812
And no SquashFS delta is installed 0.085
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.251
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.269
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.421
When the network is plugged 0.053
And Tor is ready 13.309
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 6.913
Given I shutdown Tails and wait for the computer to power off 12.490
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.975
Then Tails is running version 6.2~testoverlayfs 0.024
And all tps features are active 1.927
And the file system changes introduced in version 6.2~testoverlayfs are present 0.278
And only the 6.2~testoverlayfs SquashFS delta is installed 0.059
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.147
# 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.219
When the network is plugged 0.049
And Tor is ready 12.694
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.593
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.353
Given I shutdown Tails and wait for the computer to power off 7.399
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.636
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 1.910
And the file system changes introduced in version 6.3~testoverlayfs are present 0.375
And only the 6.3~testoverlayfs SquashFS delta is installed 0.052
# 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.161
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.221
When the network is plugged 0.085
And Tor is ready 41.091
Then the Upgrader considers the system as up-to-date 0.124
# 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 5.435
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.482
After features/support/hooks.rb:331 1.003
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
22.734
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 9.824
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.239
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.059
But a current signing key is available on our website 0.000
When the network is plugged 0.056
And Tor is ready 10.832
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.675
After features/support/hooks.rb:331 1.122
After features/support/hooks.rb:100 0.000