Project Number Date
test_Tails_ISO_devel 4526 01 Aug 2026, 11:23

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:50.054 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:12.968
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.052
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.808
When I start Tails from USB drive "old" with network unplugged 53.868
Then the boot device has safe access rights 3.476
And Tails is running from USB drive "old" 0.275
And there is no persistence partition on USB drive "old" 0.045
And process "udev-watchdog" is running 0.062
And udev-watchdog is monitoring the correct device 0.213
And I unplug USB drive "old" 0.142
After features/support/hooks.rb:339 3.640
After features/support/hooks.rb:108 0.006
Tags: @product
1:25.528
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.092
And I start Tails from USB drive "old" with network unplugged and I login 53.886
Then Tails is running from USB drive "old" 0.294
And I create a persistent partition 23.684
And I take note of which tps features are available 4.381
Then a Tails persistence partition exists on USB drive "old" 0.483
And I shutdown Tails and wait for the computer to power off 2.704
After features/support/hooks.rb:339 0.406
After features/support/hooks.rb:108 0.006
Tags: @product
1:35.799
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.046
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.312
Then Tails is running from USB drive "old" 0.429
And all tps features are active 5.484
When I write some files expected to persist 1.354
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.217
And all persistence configuration files have safe access rights 0.304
And all persistent directories from the old Tails version have safe access rights 2.103
And I take note of which tps features are available 3.743
And I shutdown Tails and wait for the computer to power off 4.040
# 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" 12.765
After features/support/hooks.rb:339 0.566
After features/support/hooks.rb:108 0.007
Tags: @product
2:10.668
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.021
And I log in to a new session 12.771
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.705
And I plug USB drive "to_upgrade" 2.232
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.519
Then the running Tails is installed on USB drive "to_upgrade" 15.063
And I unplug USB drive "to_upgrade" 0.138
And I unplug USB drive "__internal" 0.216
After features/support/hooks.rb:339 2.172
After features/support/hooks.rb:108 0.000
Tags: @product
1:14.027
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.060
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.195
Then all tps features from the old Tails version are active 0.977
And Tails is running from USB drive "to_upgrade" 0.236
And the boot device has safe access rights 2.396
And the expected persistent files created with the old Tails version are present in the filesystem 1.141
And all persistent directories from the old Tails version have safe access rights 2.020
After features/support/hooks.rb:339 0.796
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:50.384
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.408
And no SquashFS delta is installed 0.076
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.260
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.260
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.382
When the network is plugged 0.015
And Tor is ready 13.456
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.750
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.653
Given I shutdown Tails and wait for the computer to power off 5.514
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.038
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 5.172
And the file system changes introduced in version 6.2~testoverlayfs are present 0.228
And only the 6.2~testoverlayfs SquashFS delta is installed 0.034
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.138
# 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.218
When the network is plugged 0.014
And Tor is ready 10.985
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.344
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.664
Given I shutdown Tails and wait for the computer to power off 4.180
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.932
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 5.490
And the file system changes introduced in version 6.3~testoverlayfs are present 0.360
And only the 6.3~testoverlayfs SquashFS delta is installed 0.061
# 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.167
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.203
When the network is plugged 0.017
And Tor is ready 9.937
Then the Upgrader considers the system as up-to-date 10.569
# 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 4.418
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.372
After features/support/hooks.rb:339 1.116
After features/support/hooks.rb:108 0.013
Tags: @product @automatic_upgrade
20.676
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 7.328
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.331
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.014
And Tor is ready 10.296
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.621
After features/support/hooks.rb:339 0.500
After features/support/hooks.rb:108 0.000