Project Number Date
test_Tails_ISO_stable 5987 06 Dec 2025, 21:07

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:24.893 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:50.884
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.173
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.045
And I write an old version of the Tails USB image to disk "old" 28.690
When I start Tails from USB drive "old" with network unplugged 1:16.404
Then the boot device has safe access rights 3.620
And Tails is running from USB drive "old" 0.291
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.060
And udev-watchdog is monitoring the correct device 0.307
And I unplug USB drive "old" 0.175
After features/support/hooks.rb:331 4.053
After features/support/hooks.rb:100 0.009
Tags: @product
2:2.439
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.166
And I start Tails from USB drive "old" with network unplugged and I login 1:23.222
Then Tails is running from USB drive "old" 0.282
And I create a persistent partition 28.730
And I take note of which tps features are available 1.453
Then a Tails persistence partition exists on USB drive "old" 0.721
And I shutdown Tails and wait for the computer to power off 7.863
After features/support/hooks.rb:331 0.567
After features/support/hooks.rb:100 0.010
Tags: @product
2:9.590
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given a computer 0.188
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:36.181
Then Tails is running from USB drive "old" 0.669
And all tps features are active 1.925
When I write some files expected to persist 1.666
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.209
And all persistence configuration files have safe access rights 0.334
And all persistent directories from the old Tails version have safe access rights 2.218
And I take note of which tps features are available 0.525
And I shutdown Tails and wait for the computer to power off 7.800
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.868
After features/support/hooks.rb:331 0.566
After features/support/hooks.rb:100 0.017
Tags: @product
2:33.391
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 10.527
And I log in to a new session 11.122
And I clone USB drive "old" to a new USB drive "to_upgrade" 7.965
And I plug USB drive "to_upgrade" 2.426
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.813
Then the running Tails is installed on USB drive "to_upgrade" 21.510
And I unplug USB drive "to_upgrade" 0.397
And I unplug USB drive "__internal" 0.628
After features/support/hooks.rb:331 7.647
After features/support/hooks.rb:100 0.000
Tags: @product
1:24.909
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.283
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:14.959
Then all tps features from the old Tails version are active 1.749
And Tails is running from USB drive "to_upgrade" 0.319
And the boot device has safe access rights 3.682
And the expected persistent files created with the old Tails version are present in the filesystem 1.400
And all persistent directories from the old Tails version have safe access rights 2.513
After features/support/hooks.rb:331 1.340
After features/support/hooks.rb:100 0.009
4:2.870
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 9.969
And no SquashFS delta is installed 0.084
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.269
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.255
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.376
When the network is plugged 0.057
And Tor is ready 13.662
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.615
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.564
Given I shutdown Tails and wait for the computer to power off 8.046
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.898
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 2.335
And the file system changes introduced in version 6.2~testoverlayfs are present 0.379
And only the 6.2~testoverlayfs SquashFS delta is installed 0.056
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.200
# 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.284
When the network is plugged 0.054
And Tor is ready 13.100
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.789
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.122
Given I shutdown Tails and wait for the computer to power off 3.217
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.081
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.832
And the file system changes introduced in version 6.3~testoverlayfs are present 0.512
And only the 6.3~testoverlayfs SquashFS delta is installed 0.077
# 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.179
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.256
When the network is plugged 0.064
And Tor is ready 11.574
Then the Upgrader considers the system as up-to-date 0.208
# 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 7.116
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.548
After features/support/hooks.rb:331 0.762
After features/support/hooks.rb:100 0.019
20.808
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 9.442
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.053
And the signing key used by the Upgrader is outdated 0.060
But a current signing key is available on our website 0.000
When the network is plugged 0.052
And Tor is ready 9.301
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.655
After features/support/hooks.rb:331 1.049
After features/support/hooks.rb:100 0.000