Project Number Date
test_Tails_ISO_devel 4207 03 Feb 2026, 20:02

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.712 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:7.027
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.050
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" 14.021
When I start Tails from USB drive "old" with network unplugged 47.937
Then the boot device has safe access rights 3.132
And Tails is running from USB drive "old" 0.317
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.071
And udev-watchdog is monitoring the correct device 0.288
And I unplug USB drive "old" 0.136
After features/support/hooks.rb:331 1.573
After features/support/hooks.rb:100 0.005
Tags: @product
1:29.731
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.050
And I start Tails from USB drive "old" with network unplugged and I login 54.614
Then Tails is running from USB drive "old" 0.282
And I create a persistent partition 25.415
And I take note of which tps features are available 0.775
Then a Tails persistence partition exists on USB drive "old" 0.672
And I shutdown Tails and wait for the computer to power off 7.919
After features/support/hooks.rb:331 0.624
After features/support/hooks.rb:100 0.006
Tags: @product
1:29.569
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.476
Then Tails is running from USB drive "old" 0.279
And all tps features are active 1.112
When I write some files expected to persist 1.708
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.223
And all persistence configuration files have safe access rights 0.384
And all persistent directories from the old Tails version have safe access rights 2.182
And I take note of which tps features are available 0.156
And I shutdown Tails and wait for the computer to power off 8.314
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.680
After features/support/hooks.rb:331 0.263
After features/support/hooks.rb:100 0.006
Tags: @product
2:12.462
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 without a persistent partition and stopped at Tails Greeter's login screen 8.320
And I log in to a new session 11.513
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.811
And I plug USB drive "to_upgrade" 2.273
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.986
Then the running Tails is installed on USB drive "to_upgrade" 16.266
And I unplug USB drive "to_upgrade" 0.145
And I unplug USB drive "__internal" 0.145
After features/support/hooks.rb:331 2.116
After features/support/hooks.rb:100 0.000
Tags: @product
1:11.068
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.054
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.621
Then all tps features from the old Tails version are active 0.994
And Tails is running from USB drive "to_upgrade" 0.206
And the boot device has safe access rights 2.879
And the expected persistent files created with the old Tails version are present in the filesystem 1.252
And all persistent directories from the old Tails version have safe access rights 2.058
After features/support/hooks.rb:331 0.644
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
3:37.328
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 8.448
And no SquashFS delta is installed 0.072
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.280
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.236
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.451
When the network is plugged 0.020
And Tor is ready 12.503
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.555
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.645
Given I shutdown Tails and wait for the computer to power off 9.839
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.927
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.272
And the file system changes introduced in version 6.2~testoverlayfs are present 0.259
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.141
# 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.172
When the network is plugged 0.013
And Tor is ready 9.906
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.391
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.045
Given I shutdown Tails and wait for the computer to power off 4.058
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.770
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.119
And the file system changes introduced in version 6.3~testoverlayfs are present 0.354
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.152
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.204
When the network is plugged 0.020
And Tor is ready 9.868
Then the Upgrader considers the system as up-to-date 10.626
# 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.381
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.426
After features/support/hooks.rb:331 1.216
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
20.524
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.522
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.033
And the signing key used by the Upgrader is outdated 0.064
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 10.022
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.531
After features/support/hooks.rb:331 0.755
After features/support/hooks.rb:100 0.000