Project Number Date
test_Tails_ISO_devel 4676 15 Oct 2026, 11:05

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 10:53.505 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.425
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.111
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 12.815
When I start Tails from USB drive "old" with network unplugged 44.935
Then the boot device has safe access rights 1.958
And Tails is running from USB drive "old" 0.170
And there is no persistence partition on USB drive "old" 0.049
And process "udev-watchdog" is running 0.048
And udev-watchdog is monitoring the correct device 0.162
And I unplug USB drive "old" 0.130
After features/support/hooks.rb:339 3.631
After features/support/hooks.rb:108 0.005
Tags: @product
1:19.608
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.075
And I start Tails from USB drive "old" with network unplugged and I login 46.194
Then Tails is running from USB drive "old" 0.175
And I create a persistent partition 22.149
And I take note of which tps features are available 6.481
Then a Tails persistence partition exists on USB drive "old" 0.532
And I shutdown Tails and wait for the computer to power off 4.000
After features/support/hooks.rb:339 0.226
After features/support/hooks.rb:108 0.006
Tags: @product
1:28.408
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.089
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.936
Then Tails is running from USB drive "old" 0.209
And all tps features are active 6.517
When I write some files expected to persist 1.076
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.110
And all persistence configuration files have safe access rights 0.239
And all persistent directories from the old Tails version have safe access rights 1.634
And I take note of which tps features are available 6.070
And I shutdown Tails and wait for the computer to power off 2.501
# 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.019
After features/support/hooks.rb:339 0.388
After features/support/hooks.rb:108 0.005
Tags: @product
2:11.132
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.111
And I log in to a new session 11.872
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.706
And I plug USB drive "to_upgrade" 2.333
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.430
Then the running Tails is installed on USB drive "to_upgrade" 17.454
And I unplug USB drive "to_upgrade" 0.107
And I unplug USB drive "__internal" 0.116
After features/support/hooks.rb:339 1.529
After features/support/hooks.rb:108 0.000
Tags: @product
1:3.763
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.080
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.195
Then all tps features from the old Tails version are active 1.008
And Tails is running from USB drive "to_upgrade" 0.211
And the boot device has safe access rights 1.757
And the expected persistent files created with the old Tails version are present in the filesystem 0.970
And all persistent directories from the old Tails version have safe access rights 1.538
After features/support/hooks.rb:339 0.859
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:31.066
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.160
And no SquashFS delta is installed 0.067
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.225
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.222
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.338
When the network is plugged 0.023
And Tor is ready 12.217
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.624
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.198
Given I shutdown Tails and wait for the computer to power off 5.300
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.851
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.082
And the file system changes introduced in version 6.2~testoverlayfs are present 0.192
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.170
# 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.226
When the network is plugged 0.037
And Tor is ready 9.956
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.387
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.324
Given I shutdown Tails and wait for the computer to power off 2.530
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.655
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.592
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.051
# 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.083
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.191
When the network is plugged 0.025
And Tor is ready 10.213
Then the Upgrader considers the system as up-to-date 10.390
# 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 2.953
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.321
After features/support/hooks.rb:339 0.776
After features/support/hooks.rb:108 0.008
Tags: @product @automatic_upgrade
18.099
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 7.768
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.207
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
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.026
And Tor is ready 8.079
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.933
After features/support/hooks.rb:339 0.602
After features/support/hooks.rb:108 0.000