Project Number Date
test_Tails_ISO_stable 6711 30 Sep 2026, 15:22

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 11:34.443 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:1.063
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.094
And I create a 7200 MiB disk named "old" 0.029
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 14.440
When I start Tails from USB drive "old" with network unplugged 42.217
Then the boot device has safe access rights 2.642
And Tails is running from USB drive "old" 0.194
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.053
And udev-watchdog is monitoring the correct device 0.202
And I unplug USB drive "old" 0.121
After features/support/hooks.rb:339 1.136
After features/support/hooks.rb:108 0.006
Tags: @product
1:27.191
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.091
And I start Tails from USB drive "old" with network unplugged and I login 51.265
Then Tails is running from USB drive "old" 0.248
And I create a persistent partition 24.432
And I take note of which tps features are available 6.489
Then a Tails persistence partition exists on USB drive "old" 0.517
And I shutdown Tails and wait for the computer to power off 4.146
After features/support/hooks.rb:339 0.160
After features/support/hooks.rb:108 0.016
Tags: @product
1:40.015
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.098
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.363
Then Tails is running from USB drive "old" 0.332
And all tps features are active 7.869
When I write some files expected to persist 1.338
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.180
And all persistence configuration files have safe access rights 0.331
And all persistent directories from the old Tails version have safe access rights 1.859
And I take note of which tps features are available 8.226
And I shutdown Tails and wait for the computer to power off 4.396
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 12.015
After features/support/hooks.rb:339 0.349
After features/support/hooks.rb:108 0.008
Tags: @product
2:15.764
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.298
And I log in to a new session 11.020
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.972
And I plug USB drive "to_upgrade" 2.354
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.215
Then the running Tails is installed on USB drive "to_upgrade" 19.653
And I unplug USB drive "to_upgrade" 0.126
And I unplug USB drive "__internal" 0.123
After features/support/hooks.rb:339 1.681
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.932
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.090
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.798
Then all tps features from the old Tails version are active 1.481
And Tails is running from USB drive "to_upgrade" 0.218
And the boot device has safe access rights 2.462
And the expected persistent files created with the old Tails version are present in the filesystem 1.102
And all persistent directories from the old Tails version have safe access rights 1.778
After features/support/hooks.rb:339 0.756
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
3:39.329
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.592
And no SquashFS delta is installed 0.073
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.291
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.277
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.402
When the network is plugged 0.023
And Tor is ready 12.408
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.510
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.248
Given I shutdown Tails and wait for the computer to power off 6.750
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.760
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.170
And the file system changes introduced in version 6.2~testoverlayfs are present 0.271
And only the 6.2~testoverlayfs SquashFS delta is installed 0.049
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.120
# 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.178
When the network is plugged 0.032
And Tor is ready 10.437
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.317
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.609
Given I shutdown Tails and wait for the computer to power off 3.986
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.080
Then Tails is running version 6.3~testoverlayfs 0.009
And all tps features are active 8.906
And the file system changes introduced in version 6.3~testoverlayfs are present 0.333
And only the 6.3~testoverlayfs SquashFS delta is installed 0.042
# 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.100
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.160
When the network is plugged 0.028
And Tor is ready 10.640
Then the Upgrader considers the system as up-to-date 0.146
# 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 3.840
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.482
After features/support/hooks.rb:339 1.545
After features/support/hooks.rb:108 0.015
Tags: @product @automatic_upgrade
19.146
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.284
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.209
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.084
And the signing key used by the Upgrader is outdated 0.052
But a current signing key is available on our website 0.000
When the network is plugged 0.032
And Tor is ready 10.114
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.367
After features/support/hooks.rb:339 0.786
After features/support/hooks.rb:108 0.000