Project Number Date
test_Tails_ISO_stable 5985 05 Dec 2025, 20:49

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 14:49.008 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:44.696
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.203
And I create a 7200 MiB disk named "old" 0.057
And I plug USB drive "old" 1.076
And I write an old version of the Tails USB image to disk "old" 26.664
When I start Tails from USB drive "old" with network unplugged 1:12.209
Then the boot device has safe access rights 3.581
And Tails is running from USB drive "old" 0.320
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.080
And udev-watchdog is monitoring the correct device 0.265
And I unplug USB drive "old" 0.178
After features/support/hooks.rb:331 3.551
After features/support/hooks.rb:100 0.010
Tags: @product
2:3.668
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.184
And I start Tails from USB drive "old" with network unplugged and I login 1:24.441
Then Tails is running from USB drive "old" 0.344
And I create a persistent partition 28.899
And I take note of which tps features are available 1.338
Then a Tails persistence partition exists on USB drive "old" 0.846
And I shutdown Tails and wait for the computer to power off 7.613
After features/support/hooks.rb:331 0.348
After features/support/hooks.rb:100 0.010
Tags: @product
2:23.139
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.168
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:33.947
Then Tails is running from USB drive "old" 0.796
And all tps features are active 6.679
When I write some files expected to persist 1.589
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.253
And all persistence configuration files have safe access rights 0.468
And all persistent directories from the old Tails version have safe access rights 2.624
And I take note of which tps features are available 10.724
And I shutdown Tails and wait for the computer to power off 4.616
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 21.269
After features/support/hooks.rb:331 0.337
After features/support/hooks.rb:100 0.010
Tags: @product
2:27.689
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 10.086
And I log in to a new session 11.289
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.299
And I plug USB drive "to_upgrade" 3.310
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.020
Then the running Tails is installed on USB drive "to_upgrade" 21.222
And I unplug USB drive "to_upgrade" 0.230
And I unplug USB drive "__internal" 0.229
After features/support/hooks.rb:331 3.736
After features/support/hooks.rb:100 0.000
Tags: @product
1:26.424
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.171
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:16.357
Then all tps features from the old Tails version are active 1.981
And Tails is running from USB drive "to_upgrade" 0.331
And the boot device has safe access rights 3.431
And the expected persistent files created with the old Tails version are present in the filesystem 1.555
And all persistent directories from the old Tails version have safe access rights 2.595
After features/support/hooks.rb:331 1.066
After features/support/hooks.rb:100 0.035
Tags: @product @automatic_upgrade
4:21.415
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 10.728
And no SquashFS delta is installed 0.086
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.243
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.281
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.479
When the network is plugged 0.054
And Tor is ready 14.323
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.108
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.580
Given I shutdown Tails and wait for the computer to power off 8.365
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:20.925
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 4.116
And the file system changes introduced in version 6.2~testoverlayfs are present 0.285
And only the 6.2~testoverlayfs SquashFS delta is installed 0.082
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.206
# 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.247
When the network is plugged 0.073
And Tor is ready 12.498
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.034
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.365
Given I shutdown Tails and wait for the computer to power off 8.539
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:19.256
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.168
And the file system changes introduced in version 6.3~testoverlayfs are present 0.476
And only the 6.3~testoverlayfs SquashFS delta is installed 0.095
# 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.196
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.238
When the network is plugged 0.057
And Tor is ready 13.928
Then the Upgrader considers the system as up-to-date 0.127
# 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.538
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.610
After features/support/hooks.rb:331 1.229
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
21.975
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 9.651
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.273
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the signing key used by the Upgrader is outdated 0.085
But a current signing key is available on our website 0.000
When the network is plugged 0.069
And Tor is ready 9.808
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.017
After features/support/hooks.rb:331 0.998
After features/support/hooks.rb:100 0.000