Project Number Date
test_Tails_ISO_devel 4119 12 Dec 2025, 23:16

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:43.618 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.216
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.409
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.040
And I write an old version of the Tails USB image to disk "old" 33.573
When I start Tails from USB drive "old" with network unplugged 1:4.203
Then the boot device has safe access rights 3.098
And Tails is running from USB drive "old" 0.304
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.225
And I unplug USB drive "old" 0.195
After features/support/hooks.rb:331 3.814
After features/support/hooks.rb:100 0.010
Tags: @product
1:47.271
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.177
And I start Tails from USB drive "old" with network unplugged and I login 1:5.856
Then Tails is running from USB drive "old" 0.401
And I create a persistent partition 30.392
And I take note of which tps features are available 1.273
Then a Tails persistence partition exists on USB drive "old" 0.677
And I shutdown Tails and wait for the computer to power off 8.493
After features/support/hooks.rb:331 0.264
After features/support/hooks.rb:100 0.009
Tags: @product
1:53.257
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 "old" with network unplugged and I login with persistence enabled 1:18.224
Then Tails is running from USB drive "old" 0.789
And all tps features are active 1.950
When I write some files expected to persist 1.646
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.244
And all persistence configuration files have safe access rights 0.377
And all persistent directories from the old Tails version have safe access rights 2.425
And I take note of which tps features are available 0.455
And I shutdown Tails and wait for the computer to power off 7.713
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.219
After features/support/hooks.rb:331 0.316
After features/support/hooks.rb:100 0.044
Tags: @product
2:36.438
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.829
And I log in to a new session 17.273
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.221
And I plug USB drive "to_upgrade" 2.344
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.732
Then the running Tails is installed on USB drive "to_upgrade" 21.603
And I unplug USB drive "to_upgrade" 0.237
And I unplug USB drive "__internal" 0.195
After features/support/hooks.rb:331 4.469
After features/support/hooks.rb:100 0.000
Tags: @product
1:32.817
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.017
Given a computer 0.194
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:23.154
Then all tps features from the old Tails version are active 2.124
And Tails is running from USB drive "to_upgrade" 0.323
And the boot device has safe access rights 3.267
And the expected persistent files created with the old Tails version are present in the filesystem 1.495
And all persistent directories from the old Tails version have safe access rights 2.256
After features/support/hooks.rb:331 0.862
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
4:42.233
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.205
And no SquashFS delta is installed 0.087
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.083
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.236
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.488
When the network is plugged 0.054
And Tor is ready 14.887
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.486
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.786
Given I shutdown Tails and wait for the computer to power off 9.276
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:33.287
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 2.492
And the file system changes introduced in version 6.2~testoverlayfs are present 0.776
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.211
# 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.325
When the network is plugged 0.064
And Tor is ready 13.535
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.605
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.208
Given I shutdown Tails and wait for the computer to power off 4.952
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:24.256
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 3.084
And the file system changes introduced in version 6.3~testoverlayfs are present 0.616
And only the 6.3~testoverlayfs SquashFS delta is installed 0.066
# 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.274
When the network is plugged 0.057
And Tor is ready 13.015
Then the Upgrader considers the system as up-to-date 0.116
# 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.592
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.529
After features/support/hooks.rb:331 1.065
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
28.384
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.971
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.273
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.080
But a current signing key is available on our website 0.000
When the network is plugged 0.054
And Tor is ready 12.157
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.795
After features/support/hooks.rb:331 1.050
After features/support/hooks.rb:100 0.000