Project Number Date
test_Tails_ISO_devel 4134 22 Dec 2025, 12:31

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:53.182 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:18.601
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.013
Given a computer 0.206
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 26.656
When I start Tails from USB drive "old" with network unplugged 46.773
Then the boot device has safe access rights 3.044
And Tails is running from USB drive "old" 0.299
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.048
And udev-watchdog is monitoring the correct device 0.238
And I unplug USB drive "old" 0.170
After features/support/hooks.rb:331 3.626
After features/support/hooks.rb:100 0.009
Tags: @product
1:41.741
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.164
And I start Tails from USB drive "old" with network unplugged and I login 1:1.653
Then Tails is running from USB drive "old" 0.283
And I create a persistent partition 29.994
And I take note of which tps features are available 1.248
Then a Tails persistence partition exists on USB drive "old" 0.713
And I shutdown Tails and wait for the computer to power off 7.682
After features/support/hooks.rb:331 0.261
After features/support/hooks.rb:100 0.010
Tags: @product
1:46.129
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:12.541
Then Tails is running from USB drive "old" 0.380
And all tps features are active 2.007
When I write some files expected to persist 1.563
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.268
And all persistence configuration files have safe access rights 0.452
And all persistent directories from the old Tails version have safe access rights 2.384
And I take note of which tps features are available 0.680
And I shutdown Tails and wait for the computer to power off 7.860
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.796
After features/support/hooks.rb:331 0.269
After features/support/hooks.rb:100 0.009
Tags: @product
2:18.300
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 10.462
And I log in to a new session 9.426
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.418
And I plug USB drive "to_upgrade" 2.600
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.145
Then the running Tails is installed on USB drive "to_upgrade" 18.839
And I unplug USB drive "to_upgrade" 0.194
And I unplug USB drive "__internal" 0.211
After features/support/hooks.rb:331 3.596
After features/support/hooks.rb:100 0.000
Tags: @product
1:22.565
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.165
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:12.949
Then all tps features from the old Tails version are active 1.543
And Tails is running from USB drive "to_upgrade" 0.308
And the boot device has safe access rights 3.250
And the expected persistent files created with the old Tails version are present in the filesystem 1.667
And all persistent directories from the old Tails version have safe access rights 2.680
After features/support/hooks.rb:331 0.923
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
4:4.396
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 with a persistent partition enabled and logged in 9.898
And no SquashFS delta is installed 0.103
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.233
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.311
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.398
When the network is plugged 0.051
And Tor is ready 13.148
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.717
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.330
Given I shutdown Tails and wait for the computer to power off 10.775
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.775
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.139
And the file system changes introduced in version 6.2~testoverlayfs are present 0.303
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.168
# 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.328
When the network is plugged 0.063
And Tor is ready 12.427
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.634
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.820
Given I shutdown Tails and wait for the computer to power off 4.629
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.018
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.254
And the file system changes introduced in version 6.3~testoverlayfs are present 0.482
And only the 6.3~testoverlayfs SquashFS delta is installed 0.058
# 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.165
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.316
When the network is plugged 0.055
And Tor is ready 13.091
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 6.701
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.694
After features/support/hooks.rb:331 0.960
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
21.446
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 with a persistent partition enabled and logged in 9.608
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.249
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.171
And the signing key used by the Upgrader is outdated 0.475
But a current signing key is available on our website 0.000
When the network is plugged 0.069
And Tor is ready 10.279
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.593
After features/support/hooks.rb:331 0.890
After features/support/hooks.rb:100 0.000