Project Number Date
test_Tails_ISO_stable 6303 15 Apr 2026, 11:47

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 12:47.217 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.338
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.123
And I create a 7200 MiB disk named "old" 0.011
And I plug USB drive "old" 1.023
And I write an old version of the Tails USB image to disk "old" 14.154
When I start Tails from USB drive "old" with network unplugged 42.400
Then the boot device has safe access rights 2.857
And Tails is running from USB drive "old" 0.261
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.243
And I unplug USB drive "old" 0.143
After features/support/hooks.rb:331 3.777
After features/support/hooks.rb:100 0.007
Tags: @product
1:29.959
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.070
And I start Tails from USB drive "old" with network unplugged and I login 55.548
Then Tails is running from USB drive "old" 0.350
And I create a persistent partition 25.457
And I take note of which tps features are available 0.739
Then a Tails persistence partition exists on USB drive "old" 0.634
And I shutdown Tails and wait for the computer to power off 7.158
After features/support/hooks.rb:331 0.370
After features/support/hooks.rb:100 0.007
Tags: @product
1:28.933
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.063
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.598
Then Tails is running from USB drive "old" 0.339
And all tps features are active 1.131
When I write some files expected to persist 1.395
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.206
And all persistence configuration files have safe access rights 0.489
And all persistent directories from the old Tails version have safe access rights 1.883
And I take note of which tps features are available 0.168
And I shutdown Tails and wait for the computer to power off 8.023
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.633
After features/support/hooks.rb:331 0.443
After features/support/hooks.rb:100 0.007
Tags: @product
2:24.551
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 8.160
And I log in to a new session 19.786
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.764
And I plug USB drive "to_upgrade" 2.278
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.382
Then the running Tails is installed on USB drive "to_upgrade" 15.912
And I unplug USB drive "to_upgrade" 0.134
And I unplug USB drive "__internal" 0.131
After features/support/hooks.rb:331 3.733
After features/support/hooks.rb:100 0.000
Tags: @product
1:16.787
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.114
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:9.458
Then all tps features from the old Tails version are active 1.112
And Tails is running from USB drive "to_upgrade" 0.251
And the boot device has safe access rights 2.682
And the expected persistent files created with the old Tails version are present in the filesystem 1.191
And all persistent directories from the old Tails version have safe access rights 1.977
After features/support/hooks.rb:331 0.545
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:37.054
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.050
And no SquashFS delta is installed 0.114
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.312
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.234
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.415
When the network is plugged 0.026
And Tor is ready 22.565
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.386
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.914
Given I shutdown Tails and wait for the computer to power off 16.968
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.911
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.174
And the file system changes introduced in version 6.2~testoverlayfs are present 0.210
And only the 6.2~testoverlayfs SquashFS delta is installed 0.039
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.151
# 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.302
When the network is plugged 0.018
And Tor is ready 21.223
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.379
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.928
Given I shutdown Tails and wait for the computer to power off 17.678
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.807
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 1.290
And the file system changes introduced in version 6.3~testoverlayfs are present 0.383
And only the 6.3~testoverlayfs SquashFS delta is installed 0.052
# 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.151
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.209
When the network is plugged 0.015
And Tor is ready 21.214
Then the Upgrader considers the system as up-to-date 0.108
# 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 4.316
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.421
After features/support/hooks.rb:331 0.812
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
28.592
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.531
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.307
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 0.038
But a current signing key is available on our website 0.000
When the network is plugged 0.041
And Tor is ready 20.224
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.398
After features/support/hooks.rb:331 0.642
After features/support/hooks.rb:100 0.000