Project Number Date
test_Tails_ISO_devel 4037 27 Oct 2025, 21:32

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:4.849 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:43.868
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.220
And I create a 7200 MiB disk named "old" 0.063
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 26.397
When I start Tails from USB drive "old" with network unplugged 1:12.584
Then the boot device has safe access rights 2.698
And Tails is running from USB drive "old" 0.296
And there is no persistence partition on USB drive "old" 0.049
And process "udev-watchdog" is running 0.086
And udev-watchdog is monitoring the correct device 0.232
And I unplug USB drive "old" 0.180
After features/support/hooks.rb:331 3.897
After features/support/hooks.rb:100 0.009
Tags: @product
2:7.955
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.258
And I start Tails from USB drive "old" with network unplugged and I login 1:26.734
Then Tails is running from USB drive "old" 0.701
And I create a persistent partition 29.413
And I take note of which tps features are available 1.351
Then a Tails persistence partition exists on USB drive "old" 0.750
And I shutdown Tails and wait for the computer to power off 8.746
After features/support/hooks.rb:331 0.617
After features/support/hooks.rb:100 0.015
Tags: @product
2:12.951
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.229
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:38.314
Then Tails is running from USB drive "old" 0.296
And all tps features are active 2.176
When I write some files expected to persist 1.710
# 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.437
And all persistent directories from the old Tails version have safe access rights 2.190
And I take note of which tps features are available 0.576
And I shutdown Tails and wait for the computer to power off 7.672
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.148
After features/support/hooks.rb:331 0.923
After features/support/hooks.rb:100 0.062
Tags: @product
2:32.522
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.775
And I log in to a new session 17.191
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.197
And I plug USB drive "to_upgrade" 2.360
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.360
Then the running Tails is installed on USB drive "to_upgrade" 21.183
And I unplug USB drive "to_upgrade" 0.232
And I unplug USB drive "__internal" 0.220
After features/support/hooks.rb:331 4.193
After features/support/hooks.rb:100 0.000
Tags: @product
1:54.625
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.212
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:42.627
Then all tps features from the old Tails version are active 3.627
And Tails is running from USB drive "to_upgrade" 0.369
And the boot device has safe access rights 3.635
And the expected persistent files created with the old Tails version are present in the filesystem 1.566
And all persistent directories from the old Tails version have safe access rights 2.584
After features/support/hooks.rb:331 0.826
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
5:9.432
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.393
And no SquashFS delta is installed 0.078
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.291
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.308
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.512
When the network is plugged 0.066
And Tor is ready 13.638
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.669
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.046
Given I shutdown Tails and wait for the computer to power off 11.240
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:44.187
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 2.885
And the file system changes introduced in version 6.2~testoverlayfs are present 0.389
And only the 6.2~testoverlayfs SquashFS delta is installed 0.092
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.197
# 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.237
When the network is plugged 0.077
And Tor is ready 12.008
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.572
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.031
Given I shutdown Tails and wait for the computer to power off 7.930
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:43.662
Then Tails is running version 6.3~testoverlayfs 0.022
And all tps features are active 2.935
And the file system changes introduced in version 6.3~testoverlayfs are present 0.651
And only the 6.3~testoverlayfs SquashFS delta is installed 0.096
# 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.162
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.319
When the network is plugged 0.098
And Tor is ready 12.804
Then the Upgrader considers the system as up-to-date 0.189
# 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 6.007
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.571
After features/support/hooks.rb:331 0.962
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
23.492
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 10.432
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.343
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.068
But a current signing key is available on our website 0.000
When the network is plugged 0.073
And Tor is ready 11.818
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.703
After features/support/hooks.rb:331 0.906
After features/support/hooks.rb:100 0.000