Project Number Date
test_Tails_ISO_devel 4355 21 Apr 2026, 13:50

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 13:14.684 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:12.191
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.072
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 14.846
When I start Tails from USB drive "old" with network unplugged 52.628
Then the boot device has safe access rights 2.878
And Tails is running from USB drive "old" 0.284
And there is no persistence partition on USB drive "old" 0.048
And process "udev-watchdog" is running 0.063
And udev-watchdog is monitoring the correct device 0.196
And I unplug USB drive "old" 0.143
After features/support/hooks.rb:331 1.385
After features/support/hooks.rb:100 0.008
Tags: @product
1:32.032
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.072
And I start Tails from USB drive "old" with network unplugged and I login 56.488
Then Tails is running from USB drive "old" 0.247
And I create a persistent partition 25.561
And I take note of which tps features are available 0.720
Then a Tails persistence partition exists on USB drive "old" 0.538
And I shutdown Tails and wait for the computer to power off 8.403
After features/support/hooks.rb:331 0.339
After features/support/hooks.rb:100 0.007
Tags: @product
1:31.649
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.113
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.656
Then Tails is running from USB drive "old" 0.306
And all tps features are active 1.163
When I write some files expected to persist 1.404
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.200
And all persistence configuration files have safe access rights 0.479
And all persistent directories from the old Tails version have safe access rights 1.969
And I take note of which tps features are available 0.172
And I shutdown Tails and wait for the computer to power off 7.001
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.181
After features/support/hooks.rb:331 0.196
After features/support/hooks.rb:100 0.006
Tags: @product
2:18.954
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 without a persistent partition and stopped at Tails Greeter's login screen 9.012
And I log in to a new session 17.348
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.100
And I plug USB drive "to_upgrade" 2.245
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.073
Then the running Tails is installed on USB drive "to_upgrade" 16.875
And I unplug USB drive "to_upgrade" 0.161
And I unplug USB drive "__internal" 0.138
After features/support/hooks.rb:331 3.378
After features/support/hooks.rb:100 0.000
Tags: @product
1:18.455
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.114
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:10.578
Then all tps features from the old Tails version are active 0.994
And Tails is running from USB drive "to_upgrade" 0.229
And the boot device has safe access rights 2.811
And the expected persistent files created with the old Tails version are present in the filesystem 1.465
And all persistent directories from the old Tails version have safe access rights 2.261
After features/support/hooks.rb:331 0.926
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
4:53.148
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 8.988
And no SquashFS delta is installed 0.127
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.259
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.230
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.394
When the network is plugged 0.019
And Tor is ready 23.765
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.401
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.155
Given I shutdown Tails and wait for the computer to power off 20.722
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:21.304
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.238
And the file system changes introduced in version 6.2~testoverlayfs are present 0.273
And only the 6.2~testoverlayfs SquashFS delta is installed 0.059
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.157
# 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.229
When the network is plugged 0.018
And Tor is ready 20.637
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.440
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.683
Given I shutdown Tails and wait for the computer to power off 13.755
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:19.199
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.304
And the file system changes introduced in version 6.3~testoverlayfs are present 0.447
And only the 6.3~testoverlayfs SquashFS delta is installed 0.046
# 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.205
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.263
When the network is plugged 0.018
And Tor is ready 22.545
Then the Upgrader considers the system as up-to-date 0.110
# 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.679
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.404
After features/support/hooks.rb:331 0.850
After features/support/hooks.rb:100 0.026
Tags: @product @automatic_upgrade
28.251
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 8.165
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.314
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the signing key used by the Upgrader is outdated 0.046
But a current signing key is available on our website 0.000
When the network is plugged 0.019
And Tor is ready 19.215
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.446
After features/support/hooks.rb:331 1.262
After features/support/hooks.rb:100 0.000