Project Number Date
test_Tails_ISO_stable 5951 14 Nov 2025, 07:10

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 17:43.273 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
2:20.537
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.193
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.044
And I write an old version of the Tails USB image to disk "old" 37.734
When I start Tails from USB drive "old" with network unplugged 1:37.876
Then the boot device has safe access rights 2.755
And Tails is running from USB drive "old" 0.308
And there is no persistence partition on USB drive "old" 0.055
And process "udev-watchdog" is running 0.070
And udev-watchdog is monitoring the correct device 0.280
And I unplug USB drive "old" 0.171
After features/support/hooks.rb:331 4.165
After features/support/hooks.rb:100 0.023
Tags: @product
2:14.054
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given a computer 0.173
And I start Tails from USB drive "old" with network unplugged and I login 1:30.457
Then Tails is running from USB drive "old" 0.680
And I create a persistent partition 32.519
And I take note of which tps features are available 1.459
Then a Tails persistence partition exists on USB drive "old" 0.801
And I shutdown Tails and wait for the computer to power off 7.962
After features/support/hooks.rb:331 0.568
After features/support/hooks.rb:100 0.010
Tags: @product
2:15.240
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.213
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:38.825
Then Tails is running from USB drive "old" 0.690
And all tps features are active 2.103
When I write some files expected to persist 1.594
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.212
And all persistence configuration files have safe access rights 0.687
And all persistent directories from the old Tails version have safe access rights 3.017
And I take note of which tps features are available 0.463
And I shutdown Tails and wait for the computer to power off 7.996
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.435
After features/support/hooks.rb:331 0.252
After features/support/hooks.rb:100 0.008
Tags: @product
2:46.439
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 13.658
And I log in to a new session 20.337
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.063
And I plug USB drive "to_upgrade" 2.560
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:45.405
Then the running Tails is installed on USB drive "to_upgrade" 21.958
And I unplug USB drive "to_upgrade" 0.211
And I unplug USB drive "__internal" 0.242
After features/support/hooks.rb:331 4.222
After features/support/hooks.rb:100 0.000
Tags: @product
1:50.022
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.232
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:39.757
Then all tps features from the old Tails version are active 2.128
And Tails is running from USB drive "to_upgrade" 0.605
And the boot device has safe access rights 3.651
And the expected persistent files created with the old Tails version are present in the filesystem 1.438
And all persistent directories from the old Tails version have safe access rights 2.208
After features/support/hooks.rb:331 0.895
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
5:50.181
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.994
And no SquashFS delta is installed 0.080
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.300
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.295
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.460
When the network is plugged 0.075
And Tor is ready 14.971
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.628
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.118
Given I shutdown Tails and wait for the computer to power off 11.852
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:50.546
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.152
And the file system changes introduced in version 6.2~testoverlayfs are present 0.412
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.205
# 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.266
When the network is plugged 0.053
And Tor is ready 43.613
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.761
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.828
Given I shutdown Tails and wait for the computer to power off 8.253
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:43.494
Then Tails is running version 6.3~testoverlayfs 0.109
And all tps features are active 2.729
And the file system changes introduced in version 6.3~testoverlayfs are present 0.559
And only the 6.3~testoverlayfs SquashFS delta is installed 0.063
# 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.195
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.305
When the network is plugged 0.063
And Tor is ready 12.393
Then the Upgrader considers the system as up-to-date 0.206
# 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 6.440
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.610
After features/support/hooks.rb:331 1.382
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
26.797
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.679
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.396
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.080
And the signing key used by the Upgrader is outdated 0.118
But a current signing key is available on our website 0.000
When the network is plugged 0.090
And Tor is ready 12.573
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.858
After features/support/hooks.rb:331 1.072
After features/support/hooks.rb:100 0.000