Project Number Date
test_Tails_ISO_devel 4059 07 Nov 2025, 12:14

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 15:43.013 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:52.003
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.169
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 31.394
When I start Tails from USB drive "old" with network unplugged 1:15.589
Then the boot device has safe access rights 2.838
And Tails is running from USB drive "old" 0.306
And there is no persistence partition on USB drive "old" 0.091
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.271
And I unplug USB drive "old" 0.195
After features/support/hooks.rb:331 3.812
After features/support/hooks.rb:100 0.009
Tags: @product
1:59.417
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.161
And I start Tails from USB drive "old" with network unplugged and I login 1:25.254
Then Tails is running from USB drive "old" 0.274
And I create a persistent partition 28.651
And I take note of which tps features are available 1.247
Then a Tails persistence partition exists on USB drive "old" 0.624
And I shutdown Tails and wait for the computer to power off 3.202
After features/support/hooks.rb:331 0.555
After features/support/hooks.rb:100 0.009
Tags: @product
2:6.120
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:33.800
Then Tails is running from USB drive "old" 0.317
And all tps features are active 1.794
When I write some files expected to persist 1.526
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.200
And all persistence configuration files have safe access rights 0.407
And all persistent directories from the old Tails version have safe access rights 2.157
And I take note of which tps features are available 0.436
And I shutdown Tails and wait for the computer to power off 7.543
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.747
After features/support/hooks.rb:331 0.308
After features/support/hooks.rb:100 0.008
Tags: @product
2:34.873
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 without a persistent partition and stopped at Tails Greeter's login screen 13.173
And I log in to a new session 16.341
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.373
And I plug USB drive "to_upgrade" 2.537
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.379
Then the running Tails is installed on USB drive "to_upgrade" 19.674
And I unplug USB drive "to_upgrade" 0.191
And I unplug USB drive "__internal" 0.202
After features/support/hooks.rb:331 4.113
After features/support/hooks.rb:100 0.000
Tags: @product
1:44.994
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.162
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:36.337
Then all tps features from the old Tails version are active 1.341
And Tails is running from USB drive "to_upgrade" 0.290
And the boot device has safe access rights 3.005
And the expected persistent files created with the old Tails version are present in the filesystem 1.302
And all persistent directories from the old Tails version have safe access rights 2.554
After features/support/hooks.rb:331 0.950
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
5:1.084
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 with a persistent partition enabled and logged in 12.635
And no SquashFS delta is installed 0.128
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.299
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.249
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.518
When the network is plugged 0.051
And Tor is ready 14.960
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.569
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.214
Given I shutdown Tails and wait for the computer to power off 11.364
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:42.472
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 1.979
And the file system changes introduced in version 6.2~testoverlayfs are present 0.307
And only the 6.2~testoverlayfs SquashFS delta is installed 0.061
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.177
# 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.269
When the network is plugged 0.082
And Tor is ready 12.263
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.862
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.209
Given I shutdown Tails and wait for the computer to power off 7.945
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:37.743
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.273
And the file system changes introduced in version 6.3~testoverlayfs are present 0.455
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.225
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.297
When the network is plugged 0.054
And Tor is ready 12.786
Then the Upgrader considers the system as up-to-date 0.208
# 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.726
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.559
After features/support/hooks.rb:331 1.091
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
24.521
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 with a persistent partition enabled and logged in 10.576
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.313
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.068
But a current signing key is available on our website 0.000
When the network is plugged 0.056
And Tor is ready 10.565
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.887
After features/support/hooks.rb:331 0.816
After features/support/hooks.rb:100 0.000