Project Number Date
test_Tails_ISO_devel 4118 12 Dec 2025, 17:21

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 14:38.481 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:37.221
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.168
And I create a 7200 MiB disk named "old" 0.056
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 34.736
When I start Tails from USB drive "old" with network unplugged 57.227
Then the boot device has safe access rights 3.114
And Tails is running from USB drive "old" 0.265
And there is no persistence partition on USB drive "old" 0.053
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.290
And I unplug USB drive "old" 0.197
After features/support/hooks.rb:331 3.629
After features/support/hooks.rb:100 0.009
Tags: @product
1:49.267
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login 1:7.942
Then Tails is running from USB drive "old" 0.327
And I create a persistent partition 30.471
And I take note of which tps features are available 1.193
Then a Tails persistence partition exists on USB drive "old" 0.818
And I shutdown Tails and wait for the computer to power off 8.314
After features/support/hooks.rb:331 0.271
After features/support/hooks.rb:100 0.009
Tags: @product
1:54.002
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:18.632
Then Tails is running from USB drive "old" 0.674
And all tps features are active 2.115
When I write some files expected to persist 1.700
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.203
And all persistence configuration files have safe access rights 0.344
And all persistent directories from the old Tails version have safe access rights 2.289
And I take note of which tps features are available 0.540
And I shutdown Tails and wait for the computer to power off 7.810
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.500
After features/support/hooks.rb:331 0.563
After features/support/hooks.rb:100 0.012
Tags: @product
2:42.374
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.323
And I log in to a new session 16.131
And I clone USB drive "old" to a new USB drive "to_upgrade" 6.236
And I plug USB drive "to_upgrade" 2.686
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:42.818
Then the running Tails is installed on USB drive "to_upgrade" 21.756
And I unplug USB drive "to_upgrade" 0.218
And I unplug USB drive "__internal" 0.201
After features/support/hooks.rb:331 4.208
After features/support/hooks.rb:100 0.000
Tags: @product
1:31.535
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.169
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:21.111
Then all tps features from the old Tails version are active 2.002
And Tails is running from USB drive "to_upgrade" 0.301
And the boot device has safe access rights 3.417
And the expected persistent files created with the old Tails version are present in the filesystem 1.616
And all persistent directories from the old Tails version have safe access rights 2.916
After features/support/hooks.rb:331 1.014
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
4:38.814
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 13.165
And no SquashFS delta is installed 0.119
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.249
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.292
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.470
When the network is plugged 0.065
And Tor is ready 14.133
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.731
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.399
Given I shutdown Tails and wait for the computer to power off 11.285
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:36.138
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.753
And the file system changes introduced in version 6.2~testoverlayfs are present 0.345
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.181
# 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.212
When the network is plugged 0.050
And Tor is ready 12.032
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.140
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.135
Given I shutdown Tails and wait for the computer to power off 7.645
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:19.730
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 3.304
And the file system changes introduced in version 6.3~testoverlayfs are present 0.519
And only the 6.3~testoverlayfs SquashFS delta is installed 0.105
# 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.181
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.258
When the network is plugged 0.059
And Tor is ready 12.599
Then the Upgrader considers the system as up-to-date 0.186
# 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 5.557
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.615
After features/support/hooks.rb:331 0.874
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
25.265
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.970
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.290
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.069
But a current signing key is available on our website 0.000
When the network is plugged 0.066
And Tor is ready 12.118
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.691
After features/support/hooks.rb:331 1.137
After features/support/hooks.rb:100 0.000