Project Number Date
test_Tails_ISO_devel 4627 17 Sep 2026, 16:37

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:32.290 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:6.249
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.088
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.436
When I start Tails from USB drive "old" with network unplugged 48.786
Then the boot device has safe access rights 2.308
And Tails is running from USB drive "old" 0.188
And there is no persistence partition on USB drive "old" 0.033
And process "udev-watchdog" is running 0.055
And udev-watchdog is monitoring the correct device 0.187
And I unplug USB drive "old" 0.122
After features/support/hooks.rb:339 3.811
After features/support/hooks.rb:108 0.006
Tags: @product
1:24.237
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.105
And I start Tails from USB drive "old" with network unplugged and I login 49.238
Then Tails is running from USB drive "old" 0.249
And I create a persistent partition 23.264
And I take note of which tps features are available 6.586
Then a Tails persistence partition exists on USB drive "old" 0.556
And I shutdown Tails and wait for the computer to power off 4.237
After features/support/hooks.rb:339 0.642
After features/support/hooks.rb:108 0.033
Tags: @product
1:36.240
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.024
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.371
Then Tails is running from USB drive "old" 0.256
And all tps features are active 7.499
When I write some files expected to persist 0.996
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.147
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.561
And I take note of which tps features are available 6.377
And I shutdown Tails and wait for the computer to power off 3.862
# 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.737
After features/support/hooks.rb:339 0.103
After features/support/hooks.rb:108 0.006
Tags: @product
2:12.916
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 without a persistent partition and stopped at Tails Greeter's login screen 8.406
And I log in to a new session 10.993
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.623
And I plug USB drive "to_upgrade" 2.314
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.377
Then the running Tails is installed on USB drive "to_upgrade" 18.939
And I unplug USB drive "to_upgrade" 0.139
And I unplug USB drive "__internal" 0.122
After features/support/hooks.rb:339 1.738
After features/support/hooks.rb:108 0.000
Tags: @product
1:8.923
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.076
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.531
Then all tps features from the old Tails version are active 1.221
And Tails is running from USB drive "to_upgrade" 0.191
And the boot device has safe access rights 2.267
And the expected persistent files created with the old Tails version are present in the filesystem 0.948
And all persistent directories from the old Tails version have safe access rights 1.687
After features/support/hooks.rb:339 0.989
After features/support/hooks.rb:108 0.036
Tags: @product @automatic_upgrade
3:45.173
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 with a persistent partition enabled and logged in 8.602
And no SquashFS delta is installed 0.061
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.238
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.245
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.388
When the network is plugged 0.027
And Tor is ready 12.944
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.941
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.587
Given I shutdown Tails and wait for the computer to power off 6.449
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.587
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.333
And the file system changes introduced in version 6.2~testoverlayfs are present 0.193
And only the 6.2~testoverlayfs SquashFS delta is installed 0.044
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.116
# 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.228
When the network is plugged 0.028
And Tor is ready 22.691
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.300
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.920
Given I shutdown Tails and wait for the computer to power off 3.939
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.023
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 8.154
And the file system changes introduced in version 6.3~testoverlayfs are present 0.262
And only the 6.3~testoverlayfs SquashFS delta is installed 0.038
# 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.121
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.155
When the network is plugged 0.038
And Tor is ready 10.464
Then the Upgrader considers the system as up-to-date 0.126
# 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.559
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.304
After features/support/hooks.rb:339 0.647
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
18.548
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.871
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.194
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the signing key used by the Upgrader is outdated 0.039
But a current signing key is available on our website 0.000
When the network is plugged 0.035
And Tor is ready 8.699
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.660
After features/support/hooks.rb:339 0.591
After features/support/hooks.rb:108 0.000