Project Number Date
test_Tails_ISO_stable 5919 30 Oct 2025, 12:50

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:6.998 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:3.799
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.165
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.040
And I write an old version of the Tails USB image to disk "old" 31.936
When I start Tails from USB drive "old" with network unplugged 1:26.707
Then the boot device has safe access rights 2.974
And Tails is running from USB drive "old" 0.335
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.072
And udev-watchdog is monitoring the correct device 0.237
And I unplug USB drive "old" 0.223
After features/support/hooks.rb:331 3.490
After features/support/hooks.rb:100 0.012
Tags: @product
2:6.494
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.436
And I start Tails from USB drive "old" with network unplugged and I login 1:26.031
Then Tails is running from USB drive "old" 0.727
And I create a persistent partition 29.395
And I take note of which tps features are available 1.151
Then a Tails persistence partition exists on USB drive "old" 0.671
And I shutdown Tails and wait for the computer to power off 8.079
After features/support/hooks.rb:331 0.574
After features/support/hooks.rb:100 0.009
Tags: @product
2:6.326
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.181
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:36.780
Then Tails is running from USB drive "old" 0.348
And all tps features are active 2.090
When I write some files expected to persist 1.635
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.263
And all persistence configuration files have safe access rights 0.452
And all persistent directories from the old Tails version have safe access rights 2.405
And I take note of which tps features are available 0.468
And I shutdown Tails and wait for the computer to power off 3.159
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.539
After features/support/hooks.rb:331 0.166
After features/support/hooks.rb:100 0.009
Tags: @product
2:41.477
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 without a persistent partition and stopped at Tails Greeter's login screen 13.106
And I log in to a new session 18.868
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.633
And I plug USB drive "to_upgrade" 3.122
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:42.238
Then the running Tails is installed on USB drive "to_upgrade" 22.077
And I unplug USB drive "to_upgrade" 0.214
And I unplug USB drive "__internal" 0.216
After features/support/hooks.rb:331 4.077
After features/support/hooks.rb:100 0.000
Tags: @product
1:47.455
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.164
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:38.279
Then all tps features from the old Tails version are active 1.624
And Tails is running from USB drive "to_upgrade" 0.279
And the boot device has safe access rights 3.548
And the expected persistent files created with the old Tails version are present in the filesystem 1.364
And all persistent directories from the old Tails version have safe access rights 2.194
After features/support/hooks.rb:331 1.025
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
4:57.289
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 11.921
And no SquashFS delta is installed 0.096
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.325
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.103
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.491
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.522
When the network is plugged 0.059
And Tor is ready 13.998
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.859
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.913
Given I shutdown Tails and wait for the computer to power off 11.186
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:38.569
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.115
And the file system changes introduced in version 6.2~testoverlayfs are present 0.310
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.152
# 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.276
When the network is plugged 0.052
And Tor is ready 12.575
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.595
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.791
Given I shutdown Tails and wait for the computer to power off 8.049
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:38.044
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.087
And the file system changes introduced in version 6.3~testoverlayfs are present 0.471
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.161
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.234
When the network is plugged 0.056
And Tor is ready 12.408
Then the Upgrader considers the system as up-to-date 0.245
# 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.974
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.466
After features/support/hooks.rb:331 0.904
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
24.156
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 11.425
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.284
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the signing key used by the Upgrader is outdated 0.058
But a current signing key is available on our website 0.000
When the network is plugged 0.050
And Tor is ready 11.633
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.639
After features/support/hooks.rb:331 0.788
After features/support/hooks.rb:100 0.000