Project Number Date
test_Tails_ISO_devel 4631 21 Sep 2026, 11:17

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:16.627 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
58.892
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.136
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.034
And I write an old version of the Tails USB image to disk "old" 13.389
When I start Tails from USB drive "old" with network unplugged 41.732
Then the boot device has safe access rights 1.904
And Tails is running from USB drive "old" 0.302
And there is no persistence partition on USB drive "old" 0.056
And process "udev-watchdog" is running 0.041
And udev-watchdog is monitoring the correct device 0.152
And I unplug USB drive "old" 0.123
After features/support/hooks.rb:339 3.680
After features/support/hooks.rb:108 0.051
Tags: @product
1:23.666
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 49.620
Then Tails is running from USB drive "old" 0.246
And I create a persistent partition 22.320
And I take note of which tps features are available 6.704
Then a Tails persistence partition exists on USB drive "old" 0.607
And I shutdown Tails and wait for the computer to power off 4.080
After features/support/hooks.rb:339 0.187
After features/support/hooks.rb:108 0.016
Tags: @product
1:32.394
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.075
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.785
Then Tails is running from USB drive "old" 0.399
And all tps features are active 6.925
When I write some files expected to persist 0.970
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.139
And all persistence configuration files have safe access rights 0.233
And all persistent directories from the old Tails version have safe access rights 1.540
And I take note of which tps features are available 6.542
And I shutdown Tails and wait for the computer to power off 2.573
# 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.209
After features/support/hooks.rb:339 0.407
After features/support/hooks.rb:108 0.005
Tags: @product
2:12.300
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 without a persistent partition and stopped at Tails Greeter's login screen 8.547
And I log in to a new session 10.140
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.840
And I plug USB drive "to_upgrade" 2.203
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.834
Then the running Tails is installed on USB drive "to_upgrade" 18.510
And I unplug USB drive "to_upgrade" 0.114
And I unplug USB drive "__internal" 0.108
After features/support/hooks.rb:339 1.765
After features/support/hooks.rb:108 0.000
Tags: @product
1:8.106
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.087
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.389
Then all tps features from the old Tails version are active 1.012
And Tails is running from USB drive "to_upgrade" 0.227
And the boot device has safe access rights 2.373
And the expected persistent files created with the old Tails version are present in the filesystem 1.059
And all persistent directories from the old Tails version have safe access rights 1.956
After features/support/hooks.rb:339 0.540
After features/support/hooks.rb:108 0.015
Tags: @product @automatic_upgrade
3:42.004
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.619
And no SquashFS delta is installed 0.058
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.249
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.228
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.431
When the network is plugged 0.069
And Tor is ready 12.950
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.644
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.205
Given I shutdown Tails and wait for the computer to power off 5.324
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.305
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.261
And the file system changes introduced in version 6.2~testoverlayfs are present 0.222
And only the 6.2~testoverlayfs SquashFS delta is installed 0.038
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.106
# 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.216
When the network is plugged 0.050
And Tor is ready 10.391
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.868
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.985
Given I shutdown Tails and wait for the computer to power off 3.961
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.985
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 7.776
And the file system changes introduced in version 6.3~testoverlayfs are present 0.328
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.130
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.158
When the network is plugged 0.067
And Tor is ready 10.296
Then the Upgrader considers the system as up-to-date 10.366
# 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.240
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.350
After features/support/hooks.rb:339 0.888
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
19.262
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.107
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.195
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
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.032
And Tor is ready 8.382
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.436
After features/support/hooks.rb:339 0.962
After features/support/hooks.rb:108 0.000