Project Number Date
test_Tails_ISO_stable 6466 21 Jun 2026, 11:39

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:1.869 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:11.264
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.016
Given a computer 0.163
And I create a 7200 MiB disk named "old" 0.025
And I plug USB drive "old" 1.031
And I write an old version of the Tails USB image to disk "old" 13.797
When I start Tails from USB drive "old" with network unplugged 52.894
Then the boot device has safe access rights 2.599
And Tails is running from USB drive "old" 0.230
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.072
And udev-watchdog is monitoring the correct device 0.250
And I unplug USB drive "old" 0.155
After features/support/hooks.rb:339 1.241
After features/support/hooks.rb:108 0.021
Tags: @product
1:33.604
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.017
Given a computer 0.149
And I start Tails from USB drive "old" with network unplugged and I login 55.708
Then Tails is running from USB drive "old" 0.277
And I create a persistent partition 25.608
And I take note of which tps features are available 4.319
Then a Tails persistence partition exists on USB drive "old" 0.612
And I shutdown Tails and wait for the computer to power off 6.927
After features/support/hooks.rb:339 0.287
After features/support/hooks.rb:108 0.024
Tags: @product
1:34.005
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.017
Given a computer 0.139
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.264
Then Tails is running from USB drive "old" 0.327
And all tps features are active 5.278
When I write some files expected to persist 1.361
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.202
And all persistence configuration files have safe access rights 0.335
And all persistent directories from the old Tails version have safe access rights 2.143
And I take note of which tps features are available 4.337
And I shutdown Tails and wait for the computer to power off 2.782
# 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.832
After features/support/hooks.rb:339 0.288
After features/support/hooks.rb:108 0.021
Tags: @product
2:12.056
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.017
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.150
And I log in to a new session 13.133
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.738
And I plug USB drive "to_upgrade" 2.239
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.878
Then the running Tails is installed on USB drive "to_upgrade" 15.619
And I unplug USB drive "to_upgrade" 0.148
And I unplug USB drive "__internal" 0.147
After features/support/hooks.rb:339 3.635
After features/support/hooks.rb:108 0.000
Tags: @product
1:15.227
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.050
Given a computer 0.220
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.940
Then all tps features from the old Tails version are active 0.992
And Tails is running from USB drive "to_upgrade" 0.250
And the boot device has safe access rights 2.419
And the expected persistent files created with the old Tails version are present in the filesystem 1.218
And all persistent directories from the old Tails version have safe access rights 2.185
After features/support/hooks.rb:339 0.552
After features/support/hooks.rb:108 0.027
Tags: @product @automatic_upgrade
3:55.216
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.017
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.601
And no SquashFS delta is installed 0.057
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.254
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.232
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.348
When the network is plugged 0.018
And Tor is ready 13.375
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.256
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.468
Given I shutdown Tails and wait for the computer to power off 9.895
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.192
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.742
And the file system changes introduced in version 6.2~testoverlayfs are present 0.259
And only the 6.2~testoverlayfs SquashFS delta is installed 0.034
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.124
# 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.184
When the network is plugged 0.014
And Tor is ready 10.871
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.021
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.819
Given I shutdown Tails and wait for the computer to power off 6.906
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.648
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 4.807
And the file system changes introduced in version 6.3~testoverlayfs are present 0.432
And only the 6.3~testoverlayfs SquashFS delta is installed 0.036
# 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.129
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.219
When the network is plugged 0.015
And Tor is ready 10.982
Then the Upgrader considers the system as up-to-date 10.482
# 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.299
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.403
After features/support/hooks.rb:339 0.650
After features/support/hooks.rb:108 0.035
Tags: @product @automatic_upgrade
20.494
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.015
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.861
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.208
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the signing key used by the Upgrader is outdated 0.060
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 9.592
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.706
After features/support/hooks.rb:339 0.726
After features/support/hooks.rb:108 0.000