Project Number Date
test_Tails_ISO_devel 4108 08 Dec 2025, 15:45

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:4.949 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:58.374
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.181
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.043
And I write an old version of the Tails USB image to disk "old" 34.080
When I start Tails from USB drive "old" with network unplugged 1:18.471
Then the boot device has safe access rights 3.677
And Tails is running from USB drive "old" 0.316
And there is no persistence partition on USB drive "old" 0.096
And process "udev-watchdog" is running 0.055
And udev-watchdog is monitoring the correct device 0.227
And I unplug USB drive "old" 0.171
After features/support/hooks.rb:331 4.227
After features/support/hooks.rb:100 0.010
Tags: @product
2:8.870
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.167
And I start Tails from USB drive "old" with network unplugged and I login 1:27.979
Then Tails is running from USB drive "old" 0.318
And I create a persistent partition 30.726
And I take note of which tps features are available 1.351
Then a Tails persistence partition exists on USB drive "old" 0.699
And I shutdown Tails and wait for the computer to power off 7.627
After features/support/hooks.rb:331 1.225
After features/support/hooks.rb:100 0.009
Tags: @product
2:17.677
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.201
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:39.133
Then Tails is running from USB drive "old" 0.633
And all tps features are active 2.178
When I write some files expected to persist 1.893
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.199
And all persistence configuration files have safe access rights 0.423
And all persistent directories from the old Tails version have safe access rights 2.372
And I take note of which tps features are available 0.551
And I shutdown Tails and wait for the computer to power off 7.648
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 22.442
After features/support/hooks.rb:331 0.393
After features/support/hooks.rb:100 0.009
Tags: @product
2:46.174
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 13.324
And I log in to a new session 17.840
And I clone USB drive "old" to a new USB drive "to_upgrade" 7.599
And I plug USB drive "to_upgrade" 2.333
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.298
Then the running Tails is installed on USB drive "to_upgrade" 23.336
And I unplug USB drive "to_upgrade" 0.212
And I unplug USB drive "__internal" 0.229
After features/support/hooks.rb:331 3.938
After features/support/hooks.rb:100 0.000
Tags: @product
1:34.529
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.196
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:24.898
Then all tps features from the old Tails version are active 1.399
And Tails is running from USB drive "to_upgrade" 0.361
And the boot device has safe access rights 3.191
And the expected persistent files created with the old Tails version are present in the filesystem 2.042
And all persistent directories from the old Tails version have safe access rights 2.439
After features/support/hooks.rb:331 1.077
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
4:26.190
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 with a persistent partition enabled and logged in 13.721
And no SquashFS delta is installed 0.104
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.311
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.283
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.424
When the network is plugged 0.100
And Tor is ready 13.633
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.733
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.649
Given I shutdown Tails and wait for the computer to power off 11.307
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:21.108
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 2.339
And the file system changes introduced in version 6.2~testoverlayfs are present 0.288
And only the 6.2~testoverlayfs SquashFS delta is installed 0.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.169
# 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.240
When the network is plugged 0.072
And Tor is ready 12.703
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.588
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.107
Given I shutdown Tails and wait for the computer to power off 8.226
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:20.636
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.558
And the file system changes introduced in version 6.3~testoverlayfs are present 0.597
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.247
When the network is plugged 0.056
And Tor is ready 13.768
Then the Upgrader considers the system as up-to-date 0.191
# 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.067
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.558
After features/support/hooks.rb:331 1.070
After features/support/hooks.rb:100 0.045
Tags: @product @automatic_upgrade
53.131
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 11.470
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.054
And the signing key used by the Upgrader is outdated 0.060
But a current signing key is available on our website 0.000
When the network is plugged 0.057
And Tor is ready 40.604
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.634
After features/support/hooks.rb:331 1.006
After features/support/hooks.rb:100 0.000