Project Number Date
test_Tails_ISO_devel 4674 13 Oct 2026, 22: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:26.547 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:1.139
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.109
And I create a 7200 MiB disk named "old" 0.023
And I plug USB drive "old" 1.023
And I write an old version of the Tails USB image to disk "old" 14.002
When I start Tails from USB drive "old" with network unplugged 42.269
Then the boot device has safe access rights 3.023
And Tails is running from USB drive "old" 0.286
And there is no persistence partition on USB drive "old" 0.045
And process "udev-watchdog" is running 0.035
And udev-watchdog is monitoring the correct device 0.202
And I unplug USB drive "old" 0.118
After features/support/hooks.rb:339 3.433
After features/support/hooks.rb:108 0.006
Tags: @product
1:26.944
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.086
And I start Tails from USB drive "old" with network unplugged and I login 51.618
Then Tails is running from USB drive "old" 0.368
And I create a persistent partition 23.576
And I take note of which tps features are available 6.387
Then a Tails persistence partition exists on USB drive "old" 0.561
And I shutdown Tails and wait for the computer to power off 4.345
After features/support/hooks.rb:339 0.436
After features/support/hooks.rb:108 0.006
Tags: @product
1:36.271
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.082
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.620
Then Tails is running from USB drive "old" 0.236
And all tps features are active 7.598
When I write some files expected to persist 1.121
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.138
And all persistence configuration files have safe access rights 0.287
And all persistent directories from the old Tails version have safe access rights 1.536
And I take note of which tps features are available 6.302
And I shutdown Tails and wait for the computer to power off 2.770
# 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.575
After features/support/hooks.rb:339 0.537
After features/support/hooks.rb:108 0.006
Tags: @product
2:14.656
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.111
And I log in to a new session 12.515
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.783
And I plug USB drive "to_upgrade" 2.243
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.885
Then the running Tails is installed on USB drive "to_upgrade" 18.867
And I unplug USB drive "to_upgrade" 0.116
And I unplug USB drive "__internal" 0.134
After features/support/hooks.rb:339 2.002
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.171
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.093
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.209
Then all tps features from the old Tails version are active 1.192
And Tails is running from USB drive "to_upgrade" 0.226
And the boot device has safe access rights 2.310
And the expected persistent files created with the old Tails version are present in the filesystem 1.189
And all persistent directories from the old Tails version have safe access rights 1.950
After features/support/hooks.rb:339 0.561
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
3:35.669
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 with a persistent partition enabled and logged in 8.590
And no SquashFS delta is installed 0.072
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.232
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.199
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.425
When the network is plugged 0.037
And Tor is ready 12.907
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.204
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.366
Given I shutdown Tails and wait for the computer to power off 5.273
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.493
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 7.680
And the file system changes introduced in version 6.2~testoverlayfs are present 0.182
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.108
# 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.174
When the network is plugged 0.025
And Tor is ready 11.426
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.379
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.784
Given I shutdown Tails and wait for the computer to power off 4.162
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.084
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.548
And the file system changes introduced in version 6.3~testoverlayfs are present 0.346
And only the 6.3~testoverlayfs SquashFS delta is installed 0.041
# 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.113
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.186
When the network is plugged 0.024
And Tor is ready 10.571
Then the Upgrader considers the system as up-to-date 0.100
# 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 3.517
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.292
After features/support/hooks.rb:339 0.779
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
20.694
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 with a persistent partition enabled and logged in 8.708
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.277
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
And the signing key used by the Upgrader is outdated 0.050
But a current signing key is available on our website 0.000
When the network is plugged 0.033
And Tor is ready 9.869
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.718
After features/support/hooks.rb:339 1.055
After features/support/hooks.rb:108 0.000