Project Number Date
test_Tails_ISO_devel 4339 14 Apr 2026, 08:00

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:17.011 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:3.840
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.081
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 14.455
When I start Tails from USB drive "old" with network unplugged 44.830
Then the boot device has safe access rights 2.720
And Tails is running from USB drive "old" 0.274
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.051
And udev-watchdog is monitoring the correct device 0.204
And I unplug USB drive "old" 0.142
After features/support/hooks.rb:331 1.395
After features/support/hooks.rb:100 0.007
Tags: @product
1:31.206
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.056
And I start Tails from USB drive "old" with network unplugged and I login 55.676
Then Tails is running from USB drive "old" 0.288
And I create a persistent partition 25.476
And I take note of which tps features are available 0.737
Then a Tails persistence partition exists on USB drive "old" 0.605
And I shutdown Tails and wait for the computer to power off 8.367
After features/support/hooks.rb:331 0.195
After features/support/hooks.rb:100 0.008
Tags: @product
1:26.598
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.060
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.669
Then Tails is running from USB drive "old" 0.314
And all tps features are active 1.186
When I write some files expected to persist 1.322
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.191
And all persistence configuration files have safe access rights 0.459
And all persistent directories from the old Tails version have safe access rights 2.187
And I take note of which tps features are available 0.174
And I shutdown Tails and wait for the computer to power off 4.095
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.936
After features/support/hooks.rb:331 0.239
After features/support/hooks.rb:100 0.007
Tags: @product
2:18.588
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 8.612
And I log in to a new session 17.141
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.737
And I plug USB drive "to_upgrade" 2.258
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.437
Then the running Tails is installed on USB drive "to_upgrade" 17.098
And I unplug USB drive "to_upgrade" 0.143
And I unplug USB drive "__internal" 0.158
After features/support/hooks.rb:331 3.852
After features/support/hooks.rb:100 0.000
Tags: @product
1:15.617
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.050
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.302
Then all tps features from the old Tails version are active 1.037
And Tails is running from USB drive "to_upgrade" 0.286
And the boot device has safe access rights 2.648
And the expected persistent files created with the old Tails version are present in the filesystem 1.088
And all persistent directories from the old Tails version have safe access rights 2.203
After features/support/hooks.rb:331 0.637
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
5:13.460
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 21.292
And no SquashFS delta is installed 0.054
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.334
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.223
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.422
When the network is plugged 0.024
And Tor is ready 24.065
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.381
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.472
Given I shutdown Tails and wait for the computer to power off 14.143
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:19.165
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.327
And the file system changes introduced in version 6.2~testoverlayfs are present 0.208
And only the 6.2~testoverlayfs SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.127
# 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.205
When the network is plugged 0.030
And Tor is ready 20.136
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.408
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.990
Given I shutdown Tails and wait for the computer to power off 17.372
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.594
Then Tails is running version 6.3~testoverlayfs 0.009
And all tps features are active 1.285
And the file system changes introduced in version 6.3~testoverlayfs are present 0.509
And only the 6.3~testoverlayfs SquashFS delta is installed 0.062
# 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.158
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.279
When the network is plugged 0.016
And Tor is ready 39.665
Then the Upgrader considers the system as up-to-date 0.167
# 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.836
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.363
After features/support/hooks.rb:331 0.992
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
27.699
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.331
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.265
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the signing key used by the Upgrader is outdated 0.043
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 19.614
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.368
After features/support/hooks.rb:331 1.341
After features/support/hooks.rb:100 0.000