Project Number Date
test_Tails_ISO_devel 4160 09 Jan 2026, 11:36

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:22.854 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:8.842
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given a computer 0.082
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.820
When I start Tails from USB drive "old" with network unplugged 50.805
Then the boot device has safe access rights 2.410
And Tails is running from USB drive "old" 0.264
And there is no persistence partition on USB drive "old" 0.045
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.183
And I unplug USB drive "old" 0.152
After features/support/hooks.rb:331 4.056
After features/support/hooks.rb:100 0.006
Tags: @product
1:24.338
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.054
And I start Tails from USB drive "old" with network unplugged and I login 53.361
Then Tails is running from USB drive "old" 0.314
And I create a persistent partition 25.152
And I take note of which tps features are available 0.767
Then a Tails persistence partition exists on USB drive "old" 0.613
And I shutdown Tails and wait for the computer to power off 4.073
After features/support/hooks.rb:331 0.517
After features/support/hooks.rb:100 0.007
Tags: @product
1:23.259
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.013
Given a computer 0.063
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.498
Then Tails is running from USB drive "old" 0.327
And all tps features are active 1.217
When I write some files expected to persist 1.147
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.146
And all persistence configuration files have safe access rights 0.312
And all persistent directories from the old Tails version have safe access rights 1.791
And I take note of which tps features are available 0.145
And I shutdown Tails and wait for the computer to power off 4.317
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.291
After features/support/hooks.rb:331 0.570
After features/support/hooks.rb:100 0.008
Tags: @product
2:10.226
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 7.626
And I log in to a new session 11.950
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.697
And I plug USB drive "to_upgrade" 2.217
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.715
Then the running Tails is installed on USB drive "to_upgrade" 15.742
And I unplug USB drive "to_upgrade" 0.134
And I unplug USB drive "__internal" 0.141
After features/support/hooks.rb:331 7.015
After features/support/hooks.rb:100 0.000
Tags: @product
1:9.078
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 "to_upgrade" with network unplugged and I login with persistence enabled 1:2.096
Then all tps features from the old Tails version are active 0.932
And Tails is running from USB drive "to_upgrade" 0.228
And the boot device has safe access rights 2.491
And the expected persistent files created with the old Tails version are present in the filesystem 1.163
And all persistent directories from the old Tails version have safe access rights 2.117
After features/support/hooks.rb:331 0.664
After features/support/hooks.rb:100 0.025
Tags: @product @automatic_upgrade
3:45.726
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 8.824
And no SquashFS delta is installed 0.062
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.242
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.254
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.391
When the network is plugged 0.015
And Tor is ready 12.991
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.573
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.197
Given I shutdown Tails and wait for the computer to power off 11.153
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.713
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.169
And the file system changes introduced in version 6.2~testoverlayfs are present 0.192
And only the 6.2~testoverlayfs SquashFS delta is installed 0.055
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.210
# 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.227
When the network is plugged 0.017
And Tor is ready 11.109
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.960
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.421
Given I shutdown Tails and wait for the computer to power off 8.361
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.383
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.228
And the file system changes introduced in version 6.3~testoverlayfs are present 0.386
And only the 6.3~testoverlayfs SquashFS delta is installed 0.053
# 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.148
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.191
When the network is plugged 0.019
And Tor is ready 10.349
Then the Upgrader considers the system as up-to-date 10.504
# 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.845
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.415
After features/support/hooks.rb:331 0.744
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
21.383
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.596
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.196
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the signing key used by the Upgrader is outdated 0.053
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 10.026
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.423
After features/support/hooks.rb:331 0.864
After features/support/hooks.rb:100 0.000