Project Number Date
test_Tails_ISO_devel 4639 28 Sep 2026, 11:26

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:27.308 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:10.983
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.081
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.023
And I write an old version of the Tails USB image to disk "old" 13.748
When I start Tails from USB drive "old" with network unplugged 53.321
Then the boot device has safe access rights 2.170
And Tails is running from USB drive "old" 0.222
And there is no persistence partition on USB drive "old" 0.031
And process "udev-watchdog" is running 0.040
And udev-watchdog is monitoring the correct device 0.213
And I unplug USB drive "old" 0.111
After features/support/hooks.rb:339 3.544
After features/support/hooks.rb:108 0.005
Tags: @product
1:24.366
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.081
And I start Tails from USB drive "old" with network unplugged and I login 47.966
Then Tails is running from USB drive "old" 0.411
And I create a persistent partition 24.174
And I take note of which tps features are available 7.185
Then a Tails persistence partition exists on USB drive "old" 0.538
And I shutdown Tails and wait for the computer to power off 4.008
After features/support/hooks.rb:339 0.486
After features/support/hooks.rb:108 0.007
Tags: @product
1:34.515
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.091
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.935
Then Tails is running from USB drive "old" 0.194
And all tps features are active 7.473
When I write some files expected to persist 1.016
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.155
And all persistence configuration files have safe access rights 0.267
And all persistent directories from the old Tails version have safe access rights 1.649
And I take note of which tps features are available 5.859
And I shutdown Tails and wait for the computer to power off 4.067
# 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.803
After features/support/hooks.rb:339 0.295
After features/support/hooks.rb:108 0.005
Tags: @product
2:13.891
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 9.566
And I log in to a new session 11.091
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.707
And I plug USB drive "to_upgrade" 2.471
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.595
Then the running Tails is installed on USB drive "to_upgrade" 18.199
And I unplug USB drive "to_upgrade" 0.135
And I unplug USB drive "__internal" 0.124
After features/support/hooks.rb:339 1.789
After features/support/hooks.rb:108 0.000
Tags: @product
1:5.705
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.086
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.017
Then all tps features from the old Tails version are active 1.031
And Tails is running from USB drive "to_upgrade" 0.246
And the boot device has safe access rights 1.957
And the expected persistent files created with the old Tails version are present in the filesystem 0.865
And all persistent directories from the old Tails version have safe access rights 1.500
After features/support/hooks.rb:339 0.461
After features/support/hooks.rb:108 0.018
Tags: @product @automatic_upgrade
3:38.491
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.168
And no SquashFS delta is installed 0.121
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.181
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.031
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.179
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.354
When the network is plugged 0.039
And Tor is ready 11.969
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.757
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.780
Given I shutdown Tails and wait for the computer to power off 5.579
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.218
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 8.262
And the file system changes introduced in version 6.2~testoverlayfs are present 0.208
And only the 6.2~testoverlayfs SquashFS delta is installed 0.053
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.145
# 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.248
When the network is plugged 0.031
And Tor is ready 10.265
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.124
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.733
Given I shutdown Tails and wait for the computer to power off 4.348
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.053
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 7.674
And the file system changes introduced in version 6.3~testoverlayfs are present 0.388
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.111
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.169
When the network is plugged 0.037
And Tor is ready 10.363
Then the Upgrader considers the system as up-to-date 0.085
# 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.427
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.326
After features/support/hooks.rb:339 0.943
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
19.352
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.678
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.202
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the signing key used by the Upgrader is outdated 0.056
But a current signing key is available on our website 0.000
When the network is plugged 0.038
And Tor is ready 10.427
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.908
After features/support/hooks.rb:339 0.842
After features/support/hooks.rb:108 0.000