Project Number Date
test_Tails_ISO_devel 4646 30 Sep 2026, 13:52

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:45.879 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.810
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.130
And I create a 7200 MiB disk named "old" 0.035
And I plug USB drive "old" 1.024
And I write an old version of the Tails USB image to disk "old" 13.534
When I start Tails from USB drive "old" with network unplugged 54.806
Then the boot device has safe access rights 2.585
And Tails is running from USB drive "old" 0.251
And there is no persistence partition on USB drive "old" 0.049
And process "udev-watchdog" is running 0.048
And udev-watchdog is monitoring the correct device 0.225
And I unplug USB drive "old" 0.117
After features/support/hooks.rb:339 3.741
After features/support/hooks.rb:108 0.006
Tags: @product
1:28.886
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.081
And I start Tails from USB drive "old" with network unplugged and I login 52.473
Then Tails is running from USB drive "old" 0.252
And I create a persistent partition 24.880
And I take note of which tps features are available 6.669
Then a Tails persistence partition exists on USB drive "old" 0.556
And I shutdown Tails and wait for the computer to power off 3.972
After features/support/hooks.rb:339 0.577
After features/support/hooks.rb:108 0.007
Tags: @product
1:38.986
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.121
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.072
Then Tails is running from USB drive "old" 0.244
And all tps features are active 8.687
When I write some files expected to persist 1.202
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.164
And all persistence configuration files have safe access rights 0.278
And all persistent directories from the old Tails version have safe access rights 1.708
And I take note of which tps features are available 6.065
And I shutdown Tails and wait for the computer to power off 4.062
# 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" 11.378
After features/support/hooks.rb:339 0.353
After features/support/hooks.rb:108 0.005
Tags: @product
2:15.417
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 without a persistent partition and stopped at Tails Greeter's login screen 8.636
And I log in to a new session 11.331
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.788
And I plug USB drive "to_upgrade" 2.194
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.226
Then the running Tails is installed on USB drive "to_upgrade" 19.926
And I unplug USB drive "to_upgrade" 0.185
And I unplug USB drive "__internal" 0.127
After features/support/hooks.rb:339 1.683
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.789
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.097
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.733
Then all tps features from the old Tails version are active 1.160
And Tails is running from USB drive "to_upgrade" 0.217
And the boot device has safe access rights 2.453
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.935
After features/support/hooks.rb:339 0.883
After features/support/hooks.rb:108 0.030
Tags: @product @automatic_upgrade
3:39.321
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.475
And no SquashFS delta is installed 0.064
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.193
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.194
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.341
When the network is plugged 0.034
And Tor is ready 13.522
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.390
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.989
Given I shutdown Tails and wait for the computer to power off 5.415
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.229
Then Tails is running version 6.2~testoverlayfs 0.009
And all tps features are active 8.558
And the file system changes introduced in version 6.2~testoverlayfs are present 0.231
And only the 6.2~testoverlayfs SquashFS delta is installed 0.044
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.090
# 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.157
When the network is plugged 0.032
And Tor is ready 10.396
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.360
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.065
Given I shutdown Tails and wait for the computer to power off 4.077
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.173
Then Tails is running version 6.3~testoverlayfs 0.009
And all tps features are active 8.557
And the file system changes introduced in version 6.3~testoverlayfs are present 0.309
And only the 6.3~testoverlayfs SquashFS delta is installed 0.035
# 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.104
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.170
When the network is plugged 0.034
And Tor is ready 10.858
Then the Upgrader considers the system as up-to-date 0.092
# 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.730
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.327
After features/support/hooks.rb:339 1.065
After features/support/hooks.rb:108 0.013
Tags: @product @automatic_upgrade
19.667
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.287
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.219
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.026
And the signing key used by the Upgrader is outdated 0.050
But a current signing key is available on our website 0.000
When the network is plugged 0.027
And Tor is ready 9.937
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.118
After features/support/hooks.rb:339 0.519
After features/support/hooks.rb:108 0.000