Project Number Date
test_Tails_ISO_devel 4041 29 Oct 2025, 14:03

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:24.488 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:45.031
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.228
And I create a 7200 MiB disk named "old" 0.070
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 27.792
When I start Tails from USB drive "old" with network unplugged 1:11.005
Then the boot device has safe access rights 3.479
And Tails is running from USB drive "old" 0.785
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.056
And udev-watchdog is monitoring the correct device 0.298
And I unplug USB drive "old" 0.197
After features/support/hooks.rb:331 3.851
After features/support/hooks.rb:100 0.016
Tags: @product
2:10.999
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.292
And I start Tails from USB drive "old" with network unplugged and I login 1:28.712
Then Tails is running from USB drive "old" 0.309
And I create a persistent partition 31.523
And I take note of which tps features are available 1.460
Then a Tails persistence partition exists on USB drive "old" 0.883
And I shutdown Tails and wait for the computer to power off 7.817
After features/support/hooks.rb:331 0.587
After features/support/hooks.rb:100 0.008
Tags: @product
2:19.487
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.219
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:43.749
Then Tails is running from USB drive "old" 0.331
And all tps features are active 2.417
When I write some files expected to persist 1.835
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.266
And all persistence configuration files have safe access rights 0.376
And all persistent directories from the old Tails version have safe access rights 2.527
And I take note of which tps features are available 0.658
And I shutdown Tails and wait for the computer to power off 7.688
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.416
After features/support/hooks.rb:331 0.526
After features/support/hooks.rb:100 0.008
Tags: @product
2:34.506
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 without a persistent partition and stopped at Tails Greeter's login screen 10.980
And I log in to a new session 16.419
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.188
And I plug USB drive "to_upgrade" 2.339
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.048
Then the running Tails is installed on USB drive "to_upgrade" 22.125
And I unplug USB drive "to_upgrade" 0.192
And I unplug USB drive "__internal" 0.213
After features/support/hooks.rb:331 4.757
After features/support/hooks.rb:100 0.000
Tags: @product
1:53.663
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.256
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:40.095
Then all tps features from the old Tails version are active 5.337
And Tails is running from USB drive "to_upgrade" 0.342
And the boot device has safe access rights 3.327
And the expected persistent files created with the old Tails version are present in the filesystem 1.635
And all persistent directories from the old Tails version have safe access rights 2.668
After features/support/hooks.rb:331 0.760
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
5:15.009
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.512
And no SquashFS delta is installed 0.074
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.297
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.079
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.305
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.603
When the network is plugged 0.093
And Tor is ready 14.673
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.709
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.144
Given I shutdown Tails and wait for the computer to power off 11.141
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:43.645
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.916
And the file system changes introduced in version 6.2~testoverlayfs are present 0.351
And only the 6.2~testoverlayfs SquashFS delta is installed 0.089
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.186
# 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.265
When the network is plugged 0.101
And Tor is ready 12.028
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.328
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.174
Given I shutdown Tails and wait for the computer to power off 7.903
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:44.791
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.811
And the file system changes introduced in version 6.3~testoverlayfs are present 0.511
And only the 6.3~testoverlayfs SquashFS delta is installed 0.080
# 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.176
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.261
When the network is plugged 0.101
And Tor is ready 13.029
Then the Upgrader considers the system as up-to-date 0.208
# 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.874
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.503
After features/support/hooks.rb:331 0.838
After features/support/hooks.rb:100 0.026
Tags: @product @automatic_upgrade
25.789
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.443
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.257
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.118
And the signing key used by the Upgrader is outdated 0.095
But a current signing key is available on our website 0.000
When the network is plugged 0.091
And Tor is ready 13.065
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.716
After features/support/hooks.rb:331 1.263
After features/support/hooks.rb:100 0.000