Project Number Date
test_Tails_ISO_devel 4085 24 Nov 2025, 12:20

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 17:1.158 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:3.873
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 1.934
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.045
And I write an old version of the Tails USB image to disk "old" 31.013
When I start Tails from USB drive "old" with network unplugged 1:25.523
Then the boot device has safe access rights 2.897
And Tails is running from USB drive "old" 0.405
And there is no persistence partition on USB drive "old" 0.142
And process "udev-watchdog" is running 0.150
And udev-watchdog is monitoring the correct device 0.502
And I unplug USB drive "old" 0.209
After features/support/hooks.rb:331 3.979
After features/support/hooks.rb:100 0.014
Tags: @product
2:4.113
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.224
And I start Tails from USB drive "old" with network unplugged and I login 1:27.633
Then Tails is running from USB drive "old" 0.343
And I create a persistent partition 30.624
And I take note of which tps features are available 1.286
Then a Tails persistence partition exists on USB drive "old" 0.661
And I shutdown Tails and wait for the computer to power off 3.339
After features/support/hooks.rb:331 0.693
After features/support/hooks.rb:100 0.012
Tags: @product
2:17.049
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:45.589
Then Tails is running from USB drive "old" 0.312
And all tps features are active 2.011
When I write some files expected to persist 1.639
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.218
And all persistence configuration files have safe access rights 0.627
And all persistent directories from the old Tails version have safe access rights 2.550
And I take note of which tps features are available 0.493
And I shutdown Tails and wait for the computer to power off 4.771
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.639
After features/support/hooks.rb:331 0.500
After features/support/hooks.rb:100 0.011
Tags: @product
2:34.301
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.764
And I log in to a new session 13.782
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.582
And I plug USB drive "to_upgrade" 2.664
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:42.845
Then the running Tails is installed on USB drive "to_upgrade" 20.199
And I unplug USB drive "to_upgrade" 0.223
And I unplug USB drive "__internal" 0.238
After features/support/hooks.rb:331 3.765
After features/support/hooks.rb:100 0.000
Tags: @product
1:56.954
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.232
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:42.947
Then all tps features from the old Tails version are active 4.982
And Tails is running from USB drive "to_upgrade" 0.372
And the boot device has safe access rights 3.372
And the expected persistent files created with the old Tails version are present in the filesystem 1.496
And all persistent directories from the old Tails version have safe access rights 3.552
After features/support/hooks.rb:331 3.168
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
5:43.324
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 30.925
And no SquashFS delta is installed 0.081
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.247
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.288
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.517
When the network is plugged 0.054
And Tor is ready 13.437
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.862
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.042
Given I shutdown Tails and wait for the computer to power off 7.016
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:43.457
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.119
And the file system changes introduced in version 6.2~testoverlayfs are present 0.349
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.182
# 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.056
And Tor is ready 13.093
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.585
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.757
Given I shutdown Tails and wait for the computer to power off 3.509
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:35.927
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 5.086
And the file system changes introduced in version 6.3~testoverlayfs are present 0.569
And only the 6.3~testoverlayfs SquashFS delta is installed 0.094
# 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.179
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.251
When the network is plugged 0.057
And Tor is ready 41.588
Then the Upgrader considers the system as up-to-date 0.217
# 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.824
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.530
After features/support/hooks.rb:331 1.206
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
21.540
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 10.108
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.211
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.095
But a current signing key is available on our website 0.000
When the network is plugged 0.054
And Tor is ready 9.274
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.739
After features/support/hooks.rb:331 0.835
After features/support/hooks.rb:100 0.000