Project Number Date
test_Tails_ISO_stable 5914 28 Oct 2025, 09:25

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 16:41.232 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
2:11.823
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.165
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.041
And I write an old version of the Tails USB image to disk "old" 39.005
When I start Tails from USB drive "old" with network unplugged 1:27.336
Then the boot device has safe access rights 3.299
And Tails is running from USB drive "old" 0.342
And there is no persistence partition on USB drive "old" 0.077
And process "udev-watchdog" is running 0.088
And udev-watchdog is monitoring the correct device 0.213
And I unplug USB drive "old" 0.207
After features/support/hooks.rb:331 4.196
After features/support/hooks.rb:100 0.026
Tags: @product
2:5.140
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.179
And I start Tails from USB drive "old" with network unplugged and I login 1:24.835
Then Tails is running from USB drive "old" 0.617
And I create a persistent partition 29.627
And I take note of which tps features are available 1.253
Then a Tails persistence partition exists on USB drive "old" 0.717
And I shutdown Tails and wait for the computer to power off 7.909
After features/support/hooks.rb:331 0.435
After features/support/hooks.rb:100 0.010
Tags: @product
2:4.514
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 with persistence enabled 1:36.049
Then Tails is running from USB drive "old" 0.599
And all tps features are active 1.809
When I write some files expected to persist 1.508
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.186
And all persistence configuration files have safe access rights 0.325
And all persistent directories from the old Tails version have safe access rights 2.238
And I take note of which tps features are available 0.487
And I shutdown Tails and wait for the computer to power off 3.087
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.059
After features/support/hooks.rb:331 0.441
After features/support/hooks.rb:100 0.008
Tags: @product
2:37.555
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.436
And I log in to a new session 17.206
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.529
And I plug USB drive "to_upgrade" 2.401
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.082
Then the running Tails is installed on USB drive "to_upgrade" 21.468
And I unplug USB drive "to_upgrade" 0.202
And I unplug USB drive "__internal" 0.228
After features/support/hooks.rb:331 4.101
After features/support/hooks.rb:100 0.000
Tags: @product
1:50.002
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.289
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:38.744
Then all tps features from the old Tails version are active 2.721
And Tails is running from USB drive "to_upgrade" 0.683
And the boot device has safe access rights 3.585
And the expected persistent files created with the old Tails version are present in the filesystem 1.483
And all persistent directories from the old Tails version have safe access rights 2.494
After features/support/hooks.rb:331 1.071
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
5:26.898
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 13.187
And no SquashFS delta is installed 0.080
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.282
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.365
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.490
When the network is plugged 0.057
And Tor is ready 14.671
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.224
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.150
Given I shutdown Tails and wait for the computer to power off 11.658
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:46.383
Then Tails is running version 6.2~testoverlayfs 0.024
And all tps features are active 2.758
And the file system changes introduced in version 6.2~testoverlayfs are present 0.325
And only the 6.2~testoverlayfs SquashFS delta is installed 0.080
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.221
# 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.252
When the network is plugged 0.068
And Tor is ready 11.475
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.797
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.496
Given I shutdown Tails and wait for the computer to power off 3.206
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.757
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.725
And the file system changes introduced in version 6.3~testoverlayfs are present 0.472
And only the 6.3~testoverlayfs SquashFS delta is installed 0.063
# 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.253
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.262
When the network is plugged 0.056
And Tor is ready 11.191
Then the Upgrader considers the system as up-to-date 10.845
# 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.350
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.585
After features/support/hooks.rb:331 0.875
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
25.298
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 11.734
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.260
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
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.083
And Tor is ready 10.114
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.989
After features/support/hooks.rb:331 1.115
After features/support/hooks.rb:100 0.000