Project Number Date
test_Tails_ISO_stable 5989 07 Dec 2025, 19:56

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 20:36.026 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:5.913
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.202
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 32.536
When I start Tails from USB drive "old" with network unplugged 1:27.467
Then the boot device has safe access rights 3.594
And Tails is running from USB drive "old" 0.370
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.084
And udev-watchdog is monitoring the correct device 0.297
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:331 4.288
After features/support/hooks.rb:100 0.010
Tags: @product
2:4.460
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.189
And I start Tails from USB drive "old" with network unplugged and I login 1:24.609
Then Tails is running from USB drive "old" 0.286
And I create a persistent partition 29.262
And I take note of which tps features are available 1.441
Then a Tails persistence partition exists on USB drive "old" 0.835
And I shutdown Tails and wait for the computer to power off 7.835
After features/support/hooks.rb:331 0.525
After features/support/hooks.rb:100 0.009
Tags: @product
2:9.467
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.168
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:35.378
Then Tails is running from USB drive "old" 0.696
And all tps features are active 2.112
When I write some files expected to persist 1.600
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.219
And all persistence configuration files have safe access rights 0.360
And all persistent directories from the old Tails version have safe access rights 2.148
And I take note of which tps features are available 0.423
And I shutdown Tails and wait for the computer to power off 8.029
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.330
After features/support/hooks.rb:331 0.566
After features/support/hooks.rb:100 0.010
Tags: @product
3:30.475
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 13.719
And I log in to a new session 17.593
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.443
And I plug USB drive "to_upgrade" 2.491
When I upgrade Tails to USB drive "to_upgrade" by cloning 2:26.860
Then the running Tails is installed on USB drive "to_upgrade" 23.964
And I unplug USB drive "to_upgrade" 1.528
And I unplug USB drive "__internal" 1.873
After features/support/hooks.rb:331 8.245
After features/support/hooks.rb:100 0.000
Tags: @product
2:59.495
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 12.105
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:38.763
Then all tps features from the old Tails version are active 1.469
And Tails is running from USB drive "to_upgrade" 0.293
And the boot device has safe access rights 3.073
And the expected persistent files created with the old Tails version are present in the filesystem 1.440
And all persistent directories from the old Tails version have safe access rights 2.350
After features/support/hooks.rb:331 1.103
After features/support/hooks.rb:100 0.031
Tags: @product @automatic_upgrade
6:52.302
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 14.869
And no SquashFS delta is installed 0.102
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.317
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.310
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.414
When the network is plugged 0.054
And Tor is ready 24.363
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.888
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 25.809
Given I shutdown Tails and wait for the computer to power off 15.389
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.105
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 5.501
And the file system changes introduced in version 6.2~testoverlayfs are present 0.332
And only the 6.2~testoverlayfs SquashFS delta is installed 0.079
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.164
# 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.260
When the network is plugged 1.348
And Tor is ready 13.036
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.598
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.019
Given I shutdown Tails and wait for the computer to power off 7.548
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:42.585
Then Tails is running version 6.3~testoverlayfs 0.063
And all tps features are active 2.196
And the file system changes introduced in version 6.3~testoverlayfs are present 0.520
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.153
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.305
When the network is plugged 1.151
And Tor is ready 1:0.840
Then the Upgrader considers the system as up-to-date 0.253
# 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.983
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.566
After features/support/hooks.rb:331 0.998
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
53.910
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.863
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.278
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.068
But a current signing key is available on our website 0.000
When the network is plugged 0.068
And Tor is ready 41.861
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.718
After features/support/hooks.rb:331 1.210
After features/support/hooks.rb:100 0.000