Project Number Date
test_Tails_ISO_stable 5937 07 Nov 2025, 20:07

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:27.567 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:58.658
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.211
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.043
And I write an old version of the Tails USB image to disk "old" 32.262
When I start Tails from USB drive "old" with network unplugged 1:21.547
Then the boot device has safe access rights 2.710
And Tails is running from USB drive "old" 0.284
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.049
And udev-watchdog is monitoring the correct device 0.268
And I unplug USB drive "old" 0.174
After features/support/hooks.rb:331 3.675
After features/support/hooks.rb:100 0.017
Tags: @product
2:7.750
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.159
And I start Tails from USB drive "old" with network unplugged and I login 1:29.239
Then Tails is running from USB drive "old" 0.715
And I create a persistent partition 30.474
And I take note of which tps features are available 1.470
Then a Tails persistence partition exists on USB drive "old" 0.743
And I shutdown Tails and wait for the computer to power off 4.947
After features/support/hooks.rb:331 0.235
After features/support/hooks.rb:100 0.009
Tags: @product
2:6.641
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.165
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:37.018
Then Tails is running from USB drive "old" 0.317
And all tps features are active 1.963
When I write some files expected to persist 1.769
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.276
And all persistence configuration files have safe access rights 0.392
And all persistent directories from the old Tails version have safe access rights 2.456
And I take note of which tps features are available 0.524
And I shutdown Tails and wait for the computer to power off 3.194
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.562
After features/support/hooks.rb:331 0.294
After features/support/hooks.rb:100 0.009
Tags: @product
2:41.102
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 without a persistent partition and stopped at Tails Greeter's login screen 13.405
And I log in to a new session 18.288
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.464
And I plug USB drive "to_upgrade" 2.865
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:42.197
Then the running Tails is installed on USB drive "to_upgrade" 22.479
And I unplug USB drive "to_upgrade" 0.197
And I unplug USB drive "__internal" 0.203
After features/support/hooks.rb:331 3.990
After features/support/hooks.rb:100 0.000
Tags: @product
1:49.017
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.182
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:38.651
Then all tps features from the old Tails version are active 1.955
And Tails is running from USB drive "to_upgrade" 0.515
And the boot device has safe access rights 3.410
And the expected persistent files created with the old Tails version are present in the filesystem 1.696
And all persistent directories from the old Tails version have safe access rights 2.605
After features/support/hooks.rb:331 1.013
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
5:17.241
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 13.654
And no SquashFS delta is installed 0.124
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.311
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.261
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.431
When the network is plugged 0.079
And Tor is ready 14.345
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.310
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.174
Given I shutdown Tails and wait for the computer to power off 11.177
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:46.381
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.687
And the file system changes introduced in version 6.2~testoverlayfs are present 0.299
And only the 6.2~testoverlayfs SquashFS delta is installed 0.087
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.151
# 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.311
When the network is plugged 0.077
And Tor is ready 11.734
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.226
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.393
Given I shutdown Tails and wait for the computer to power off 7.571
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:44.402
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.634
And the file system changes introduced in version 6.3~testoverlayfs are present 0.516
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.222
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.249
When the network is plugged 0.062
And Tor is ready 13.051
Then the Upgrader considers the system as up-to-date 0.211
# 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.358
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.597
After features/support/hooks.rb:331 0.963
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
27.154
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.401
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.289
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.059
But a current signing key is available on our website 0.000
When the network is plugged 0.054
And Tor is ready 14.517
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.775
After features/support/hooks.rb:331 1.389
After features/support/hooks.rb:100 0.000