Project Number Date
test_Tails_ISO_devel 4083 22 Nov 2025, 12:09

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:53.336 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:59.772
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given a computer 3.453
And I create a 7200 MiB disk named "old" 0.054
And I plug USB drive "old" 1.043
And I write an old version of the Tails USB image to disk "old" 34.769
When I start Tails from USB drive "old" with network unplugged 1:16.567
Then the boot device has safe access rights 3.078
And Tails is running from USB drive "old" 0.297
And there is no persistence partition on USB drive "old" 0.053
And process "udev-watchdog" is running 0.073
And udev-watchdog is monitoring the correct device 0.215
And I unplug USB drive "old" 0.165
After features/support/hooks.rb:331 3.522
After features/support/hooks.rb:100 0.009
Tags: @product
2:11.319
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 "old" with network unplugged and I login 1:23.675
Then Tails is running from USB drive "old" 0.330
And I create a persistent partition 29.461
And I take note of which tps features are available 8.513
Then a Tails persistence partition exists on USB drive "old" 1.125
And I shutdown Tails and wait for the computer to power off 8.050
After features/support/hooks.rb:331 0.742
After features/support/hooks.rb:100 0.011
Tags: @product
2:3.595
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.246
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:33.635
Then Tails is running from USB drive "old" 0.288
And all tps features are active 1.816
When I write some files expected to persist 1.742
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.257
And all persistence configuration files have safe access rights 0.397
And all persistent directories from the old Tails version have safe access rights 2.432
And I take note of which tps features are available 0.456
And I shutdown Tails and wait for the computer to power off 4.721
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.601
After features/support/hooks.rb:331 0.364
After features/support/hooks.rb:100 0.018
Tags: @product
2:25.807
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.525
And I log in to a new session 10.347
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.621
And I plug USB drive "to_upgrade" 2.517
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.777
Then the running Tails is installed on USB drive "to_upgrade" 18.606
And I unplug USB drive "to_upgrade" 0.206
And I unplug USB drive "__internal" 0.204
After features/support/hooks.rb:331 3.530
After features/support/hooks.rb:100 0.000
Tags: @product
1:49.668
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 "to_upgrade" with network unplugged and I login with persistence enabled 1:40.706
Then all tps features from the old Tails version are active 1.467
And Tails is running from USB drive "to_upgrade" 0.286
And the boot device has safe access rights 3.338
And the expected persistent files created with the old Tails version are present in the filesystem 1.460
And all persistent directories from the old Tails version have safe access rights 2.243
After features/support/hooks.rb:331 0.696
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
4:56.316
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 12.769
And no SquashFS delta is installed 0.076
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.285
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.308
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.432
When the network is plugged 0.068
And Tor is ready 12.463
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.719
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.701
Given I shutdown Tails and wait for the computer to power off 9.569
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:46.729
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.322
And the file system changes introduced in version 6.2~testoverlayfs are present 0.365
And only the 6.2~testoverlayfs SquashFS delta is installed 0.103
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.210
# 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.386
When the network is plugged 0.061
And Tor is ready 12.625
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.582
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.196
Given I shutdown Tails and wait for the computer to power off 7.639
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:34.499
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.148
And the file system changes introduced in version 6.3~testoverlayfs are present 0.432
And only the 6.3~testoverlayfs SquashFS delta is installed 0.086
# 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.176
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.269
When the network is plugged 0.072
And Tor is ready 12.512
Then the Upgrader considers the system as up-to-date 0.207
# 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.675
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.542
After features/support/hooks.rb:331 0.982
After features/support/hooks.rb:100 0.028
Tags: @product @automatic_upgrade
26.855
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 14.640
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.244
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the signing key used by the Upgrader is outdated 0.073
But a current signing key is available on our website 0.000
When the network is plugged 0.780
And Tor is ready 10.480
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.594
After features/support/hooks.rb:331 1.051
After features/support/hooks.rb:100 0.000