Project Number Date
test_Tails_ISO_devel 4086 25 Nov 2025, 02:09

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 16:40.067 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
2:2.430
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.218
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.066
And I write an old version of the Tails USB image to disk "old" 33.279
When I start Tails from USB drive "old" with network unplugged 1:23.824
Then the boot device has safe access rights 2.962
And Tails is running from USB drive "old" 0.330
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.089
And udev-watchdog is monitoring the correct device 0.331
And I unplug USB drive "old" 0.205
After features/support/hooks.rb:331 3.901
After features/support/hooks.rb:100 0.013
Tags: @product
2:9.887
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.228
And I start Tails from USB drive "old" with network unplugged and I login 1:27.161
Then Tails is running from USB drive "old" 0.329
And I create a persistent partition 31.375
And I take note of which tps features are available 2.054
Then a Tails persistence partition exists on USB drive "old" 0.691
And I shutdown Tails and wait for the computer to power off 8.045
After features/support/hooks.rb:331 0.217
After features/support/hooks.rb:100 0.011
Tags: @product
2:27.384
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 2.466
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:50.825
Then Tails is running from USB drive "old" 0.393
And all tps features are active 2.096
When I write some files expected to persist 1.612
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.249
And all persistence configuration files have safe access rights 0.349
And all persistent directories from the old Tails version have safe access rights 2.099
And I take note of which tps features are available 0.448
And I shutdown Tails and wait for the computer to power off 7.910
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.932
After features/support/hooks.rb:331 0.679
After features/support/hooks.rb:100 0.013
Tags: @product
2:23.457
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.020
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.171
And I log in to a new session 11.107
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.267
And I plug USB drive "to_upgrade" 2.816
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.282
Then the running Tails is installed on USB drive "to_upgrade" 20.343
And I unplug USB drive "to_upgrade" 0.264
And I unplug USB drive "__internal" 0.205
After features/support/hooks.rb:331 3.625
After features/support/hooks.rb:100 0.000
Tags: @product
2:1.097
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.185
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:47.309
Then all tps features from the old Tails version are active 2.316
And Tails is running from USB drive "to_upgrade" 1.197
And the boot device has safe access rights 6.006
And the expected persistent files created with the old Tails version are present in the filesystem 1.594
And all persistent directories from the old Tails version have safe access rights 2.487
After features/support/hooks.rb:331 0.844
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
5:13.075
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 14.003
And no SquashFS delta is installed 0.100
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.309
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.303
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.467
When the network is plugged 0.083
And Tor is ready 12.907
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.950
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.912
Given I shutdown Tails and wait for the computer to power off 8.192
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:47.668
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.704
And the file system changes introduced in version 6.2~testoverlayfs are present 0.315
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.208
# 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.312
When the network is plugged 0.063
And Tor is ready 11.836
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.257
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.687
Given I shutdown Tails and wait for the computer to power off 5.380
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:46.554
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 2.456
And the file system changes introduced in version 6.3~testoverlayfs are present 0.478
And only the 6.3~testoverlayfs SquashFS delta is installed 0.064
# 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.149
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.365
When the network is plugged 0.061
And Tor is ready 12.355
Then the Upgrader considers the system as up-to-date 0.238
# 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.048
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.481
After features/support/hooks.rb:331 0.847
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
22.734
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.364
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.048
And the signing key used by the Upgrader is outdated 0.074
But a current signing key is available on our website 0.000
When the network is plugged 0.052
And Tor is ready 9.929
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.027
After features/support/hooks.rb:331 1.168
After features/support/hooks.rb:100 0.000