Project Number Date
test_Tails_ISO_devel 4144 31 Dec 2025, 13:27

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 13:58.475 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:25.274
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.166
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.038
And I write an old version of the Tails USB image to disk "old" 31.240
When I start Tails from USB drive "old" with network unplugged 48.608
Then the boot device has safe access rights 3.208
And Tails is running from USB drive "old" 0.341
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.067
And udev-watchdog is monitoring the correct device 0.291
And I unplug USB drive "old" 0.204
After features/support/hooks.rb:331 4.038
After features/support/hooks.rb:100 0.022
Tags: @product
1:43.367
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.160
And I start Tails from USB drive "old" with network unplugged and I login 1:2.483
Then Tails is running from USB drive "old" 0.294
And I create a persistent partition 30.530
And I take note of which tps features are available 1.268
Then a Tails persistence partition exists on USB drive "old" 0.791
And I shutdown Tails and wait for the computer to power off 7.837
After features/support/hooks.rb:331 0.650
After features/support/hooks.rb:100 0.009
Tags: @product
1:45.476
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.159
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:12.408
Then Tails is running from USB drive "old" 0.350
And all tps features are active 1.933
When I write some files expected to persist 1.615
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.209
And all persistence configuration files have safe access rights 0.472
And all persistent directories from the old Tails version have safe access rights 2.308
And I take note of which tps features are available 0.480
And I shutdown Tails and wait for the computer to power off 7.569
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.967
After features/support/hooks.rb:331 0.403
After features/support/hooks.rb:100 0.010
Tags: @product
2:33.770
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 11.949
And I log in to a new session 14.877
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.819
And I plug USB drive "to_upgrade" 2.727
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.080
Then the running Tails is installed on USB drive "to_upgrade" 20.915
And I unplug USB drive "to_upgrade" 0.194
And I unplug USB drive "__internal" 0.205
After features/support/hooks.rb:331 3.540
After features/support/hooks.rb:100 0.000
Tags: @product
1:25.174
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.192
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:16.629
Then all tps features from the old Tails version are active 1.391
And Tails is running from USB drive "to_upgrade" 0.298
And the boot device has safe access rights 3.114
And the expected persistent files created with the old Tails version are present in the filesystem 1.355
And all persistent directories from the old Tails version have safe access rights 2.191
After features/support/hooks.rb:331 0.845
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
4:12.773
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 12.098
And no SquashFS delta is installed 0.079
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.254
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.263
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.454
When the network is plugged 0.061
And Tor is ready 13.480
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.841
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.106
Given I shutdown Tails and wait for the computer to power off 11.409
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.775
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 2.078
And the file system changes introduced in version 6.2~testoverlayfs are present 0.341
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.152
# 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.223
When the network is plugged 0.082
And Tor is ready 12.720
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.631
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.709
Given I shutdown Tails and wait for the computer to power off 7.579
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.515
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.901
And the file system changes introduced in version 6.3~testoverlayfs are present 0.390
And only the 6.3~testoverlayfs SquashFS delta is installed 0.061
# 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.146
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.251
When the network is plugged 0.052
And Tor is ready 12.645
Then the Upgrader considers the system as up-to-date 0.168
# 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 5.682
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.466
After features/support/hooks.rb:331 0.896
After features/support/hooks.rb:100 0.028
Tags: @product @automatic_upgrade
52.638
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 10.877
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.270
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the signing key used by the Upgrader is outdated 0.069
But a current signing key is available on our website 0.000
When the network is plugged 0.052
And Tor is ready 40.709
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.602
After features/support/hooks.rb:331 0.811
After features/support/hooks.rb:100 0.000