Project Number Date
test_Tails_ISO_devel 4619 16 Sep 2026, 11:21

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:21.524 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:9.837
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given a computer 0.091
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.713
When I start Tails from USB drive "old" with network unplugged 52.405
Then the boot device has safe access rights 2.018
And Tails is running from USB drive "old" 0.191
And there is no persistence partition on USB drive "old" 0.049
And process "udev-watchdog" is running 0.033
And udev-watchdog is monitoring the correct device 0.168
And I unplug USB drive "old" 0.125
After features/support/hooks.rb:339 3.696
After features/support/hooks.rb:108 0.011
Tags: @product
1:22.504
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.076
And I start Tails from USB drive "old" with network unplugged and I login 47.301
Then Tails is running from USB drive "old" 0.187
And I create a persistent partition 23.982
And I take note of which tps features are available 6.251
Then a Tails persistence partition exists on USB drive "old" 0.562
And I shutdown Tails and wait for the computer to power off 4.142
After features/support/hooks.rb:339 0.327
After features/support/hooks.rb:108 0.005
Tags: @product
1:35.240
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.082
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.824
Then Tails is running from USB drive "old" 0.179
And all tps features are active 8.038
When I write some files expected to persist 1.149
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.184
And all persistence configuration files have safe access rights 0.295
And all persistent directories from the old Tails version have safe access rights 1.773
And I take note of which tps features are available 5.940
And I shutdown Tails and wait for the computer to power off 5.005
# 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.765
After features/support/hooks.rb:339 0.104
After features/support/hooks.rb:108 0.007
Tags: @product
2:13.645
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.289
And I log in to a new session 11.946
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.019
And I plug USB drive "to_upgrade" 2.207
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.620
Then the running Tails is installed on USB drive "to_upgrade" 18.276
And I unplug USB drive "to_upgrade" 0.154
And I unplug USB drive "__internal" 0.131
After features/support/hooks.rb:339 1.768
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.182
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.143
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.159
Then all tps features from the old Tails version are active 1.141
And Tails is running from USB drive "to_upgrade" 0.227
And the boot device has safe access rights 2.155
And the expected persistent files created with the old Tails version are present in the filesystem 0.840
And all persistent directories from the old Tails version have safe access rights 1.514
After features/support/hooks.rb:339 0.484
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:32.185
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.591
And no SquashFS delta is installed 0.062
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.197
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.028
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.209
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.351
When the network is plugged 0.050
And Tor is ready 12.810
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.299
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.555
Given I shutdown Tails and wait for the computer to power off 5.385
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.134
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 7.739
And the file system changes introduced in version 6.2~testoverlayfs are present 0.150
And only the 6.2~testoverlayfs SquashFS delta is installed 0.054
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.123
# 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.161
When the network is plugged 0.020
And Tor is ready 10.603
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.955
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.984
Given I shutdown Tails and wait for the computer to power off 4.055
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.724
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 7.856
And the file system changes introduced in version 6.3~testoverlayfs are present 0.290
And only the 6.3~testoverlayfs SquashFS delta is installed 0.043
# 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.103
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.191
When the network is plugged 0.024
And Tor is ready 10.475
Then the Upgrader considers the system as up-to-date 0.072
# 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.531
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.330
After features/support/hooks.rb:339 0.710
After features/support/hooks.rb:108 0.017
Tags: @product @automatic_upgrade
18.927
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 8.012
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.175
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 0.042
But a current signing key is available on our website 0.000
When the network is plugged 0.040
And Tor is ready 9.583
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.021
After features/support/hooks.rb:339 0.778
After features/support/hooks.rb:108 0.000