Project Number Date
test_Tails_ISO_devel 4504 21 Jul 2026, 18:34

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:31.593 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:7.608
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.066
And I create a 7200 MiB disk named "old" 0.012
And I plug USB drive "old" 1.023
And I write an old version of the Tails USB image to disk "old" 14.243
When I start Tails from USB drive "old" with network unplugged 48.463
Then the boot device has safe access rights 3.079
And Tails is running from USB drive "old" 0.234
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.045
And udev-watchdog is monitoring the correct device 0.254
And I unplug USB drive "old" 0.139
After features/support/hooks.rb:339 3.542
After features/support/hooks.rb:108 0.008
Tags: @product
1:37.369
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.061
And I start Tails from USB drive "old" with network unplugged and I login 58.326
Then Tails is running from USB drive "old" 0.271
And I create a persistent partition 25.754
And I take note of which tps features are available 4.856
Then a Tails persistence partition exists on USB drive "old" 0.717
And I shutdown Tails and wait for the computer to power off 7.382
After features/support/hooks.rb:339 0.572
After features/support/hooks.rb:108 0.007
Tags: @product
1:45.406
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.060
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:9.001
Then Tails is running from USB drive "old" 0.288
And all tps features are active 5.696
When I write some files expected to persist 1.577
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.222
And all persistence configuration files have safe access rights 0.348
And all persistent directories from the old Tails version have safe access rights 2.215
And I take note of which tps features are available 4.714
And I shutdown Tails and wait for the computer to power off 8.364
# 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.915
After features/support/hooks.rb:339 0.445
After features/support/hooks.rb:108 0.008
Tags: @product
2:17.379
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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.224
And I log in to a new session 14.806
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.297
And I plug USB drive "to_upgrade" 2.297
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.960
Then the running Tails is installed on USB drive "to_upgrade" 17.338
And I unplug USB drive "to_upgrade" 0.242
And I unplug USB drive "__internal" 0.212
After features/support/hooks.rb:339 2.359
After features/support/hooks.rb:108 0.000
Tags: @product
1:19.112
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.083
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:11.620
Then all tps features from the old Tails version are active 1.056
And Tails is running from USB drive "to_upgrade" 0.229
And the boot device has safe access rights 2.872
And the expected persistent files created with the old Tails version are present in the filesystem 1.283
And all persistent directories from the old Tails version have safe access rights 1.966
After features/support/hooks.rb:339 0.657
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
4:3.385
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.544
And no SquashFS delta is installed 0.112
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.275
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.242
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.440
When the network is plugged 0.014
And Tor is ready 14.535
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.912
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.697
Given I shutdown Tails and wait for the computer to power off 7.156
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.618
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 5.230
And the file system changes introduced in version 6.2~testoverlayfs are present 0.198
And only the 6.2~testoverlayfs SquashFS delta is installed 0.050
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.129
# 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.184
When the network is plugged 0.017
And Tor is ready 10.383
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.555
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.817
Given I shutdown Tails and wait for the computer to power off 4.080
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.986
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 5.610
And the file system changes introduced in version 6.3~testoverlayfs are present 0.347
And only the 6.3~testoverlayfs SquashFS delta is installed 0.043
# 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.137
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.205
When the network is plugged 0.013
And Tor is ready 10.548
Then the Upgrader considers the system as up-to-date 10.496
# 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.265
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.470
After features/support/hooks.rb:339 1.105
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
21.330
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 7.862
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.236
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.051
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 10.380
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.732
After features/support/hooks.rb:339 1.298
After features/support/hooks.rb:108 0.000