Project Number Date
test_Tails_ISO_devel 4352 20 Apr 2026, 11:20

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 12:31.664 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.504
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.057
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.840
When I start Tails from USB drive "old" with network unplugged 50.912
Then the boot device has safe access rights 2.987
And Tails is running from USB drive "old" 0.236
And there is no persistence partition on USB drive "old" 0.045
And process "udev-watchdog" is running 0.066
And udev-watchdog is monitoring the correct device 0.192
And I unplug USB drive "old" 0.143
After features/support/hooks.rb:331 1.338
After features/support/hooks.rb:100 0.006
Tags: @product
1:22.715
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.071
And I start Tails from USB drive "old" with network unplugged and I login 53.107
Then Tails is running from USB drive "old" 0.266
And I create a persistent partition 23.906
And I take note of which tps features are available 0.686
Then a Tails persistence partition exists on USB drive "old" 0.554
And I shutdown Tails and wait for the computer to power off 4.122
After features/support/hooks.rb:331 0.137
After features/support/hooks.rb:100 0.007
Tags: @product
1:26.203
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.048
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.666
Then Tails is running from USB drive "old" 0.291
And all tps features are active 1.073
When I write some files expected to persist 1.324
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.192
And all persistence configuration files have safe access rights 0.438
And all persistent directories from the old Tails version have safe access rights 1.943
And I take note of which tps features are available 0.134
And I shutdown Tails and wait for the computer to power off 7.788
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.302
After features/support/hooks.rb:331 0.158
After features/support/hooks.rb:100 0.006
Tags: @product
2:23.314
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 7.517
And I log in to a new session 19.763
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.786
And I plug USB drive "to_upgrade" 2.247
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.006
Then the running Tails is installed on USB drive "to_upgrade" 15.719
And I unplug USB drive "to_upgrade" 0.134
And I unplug USB drive "__internal" 0.139
After features/support/hooks.rb:331 8.899
After features/support/hooks.rb:100 0.000
Tags: @product
1:11.479
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.056
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.889
Then all tps features from the old Tails version are active 1.078
And Tails is running from USB drive "to_upgrade" 0.223
And the boot device has safe access rights 2.416
And the expected persistent files created with the old Tails version are present in the filesystem 1.076
And all persistent directories from the old Tails version have safe access rights 1.738
After features/support/hooks.rb:331 0.837
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
4:30.250
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.753
And no SquashFS delta is installed 0.107
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.424
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.218
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.386
When the network is plugged 0.032
And Tor is ready 22.439
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.348
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.717
Given I shutdown Tails and wait for the computer to power off 22.249
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.256
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.311
And the file system changes introduced in version 6.2~testoverlayfs are present 0.206
And only the 6.2~testoverlayfs SquashFS delta is installed 0.042
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.137
# 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.176
When the network is plugged 0.015
And Tor is ready 21.049
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.382
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.246
Given I shutdown Tails and wait for the computer to power off 17.199
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.432
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.081
And the file system changes introduced in version 6.3~testoverlayfs are present 0.494
And only the 6.3~testoverlayfs SquashFS delta is installed 0.047
# 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.123
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.172
When the network is plugged 0.016
And Tor is ready 20.431
Then the Upgrader considers the system as up-to-date 0.131
# 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.196
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.361
After features/support/hooks.rb:331 0.797
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
28.195
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.621
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.261
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.043
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 19.817
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.384
After features/support/hooks.rb:331 0.756
After features/support/hooks.rb:100 0.000