Project Number Date
test_Tails_ISO_devel 4081 20 Nov 2025, 16:01

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:56.944 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:1.235
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.196
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.044
And I write an old version of the Tails USB image to disk "old" 43.429
When I start Tails from USB drive "old" with network unplugged 1:12.626
Then the boot device has safe access rights 2.955
And Tails is running from USB drive "old" 0.324
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.067
And udev-watchdog is monitoring the correct device 0.278
And I unplug USB drive "old" 0.196
After features/support/hooks.rb:331 3.689
After features/support/hooks.rb:100 0.012
Tags: @product
2:13.236
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.181
And I start Tails from USB drive "old" with network unplugged and I login 1:29.022
Then Tails is running from USB drive "old" 0.900
And I create a persistent partition 32.711
And I take note of which tps features are available 1.556
Then a Tails persistence partition exists on USB drive "old" 1.081
And I shutdown Tails and wait for the computer to power off 7.782
After features/support/hooks.rb:331 0.338
After features/support/hooks.rb:100 0.010
Tags: @product
2:20.824
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.176
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:43.321
Then Tails is running from USB drive "old" 0.323
And all tps features are active 3.933
When I write some files expected to persist 2.088
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.348
And all persistence configuration files have safe access rights 0.396
And all persistent directories from the old Tails version have safe access rights 2.808
And I take note of which tps features are available 0.551
And I shutdown Tails and wait for the computer to power off 7.703
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.174
After features/support/hooks.rb:331 0.168
After features/support/hooks.rb:100 0.011
Tags: @product
2:47.938
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 9.883
And I log in to a new session 12.849
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.512
And I plug USB drive "to_upgrade" 2.372
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:58.905
Then the running Tails is installed on USB drive "to_upgrade" 19.643
And I unplug USB drive "to_upgrade" 0.666
And I unplug USB drive "__internal" 1.105
After features/support/hooks.rb:331 3.728
After features/support/hooks.rb:100 0.000
Tags: @product
1:55.699
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.199
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:45.717
Then all tps features from the old Tails version are active 1.853
And Tails is running from USB drive "to_upgrade" 0.309
And the boot device has safe access rights 3.117
And the expected persistent files created with the old Tails version are present in the filesystem 1.327
And all persistent directories from the old Tails version have safe access rights 3.173
After features/support/hooks.rb:331 0.892
After features/support/hooks.rb:100 0.019
5:12.693
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 with a persistent partition enabled and logged in 12.526
And no SquashFS delta is installed 0.122
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.240
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.285
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.459
When the network is plugged 0.061
And Tor is ready 13.960
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.701
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.155
Given I shutdown Tails and wait for the computer to power off 10.270
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:50.212
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 3.128
And the file system changes introduced in version 6.2~testoverlayfs are present 0.384
And only the 6.2~testoverlayfs SquashFS delta is installed 0.102
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.165
# 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.318
When the network is plugged 0.061
And Tor is ready 11.668
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.992
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.117
Given I shutdown Tails and wait for the computer to power off 4.001
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:42.129
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 2.573
And the file system changes introduced in version 6.3~testoverlayfs are present 0.421
And only the 6.3~testoverlayfs SquashFS delta is installed 0.087
# 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.166
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.247
When the network is plugged 0.051
And Tor is ready 14.339
Then the Upgrader considers the system as up-to-date 0.220
# 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.974
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.473
After features/support/hooks.rb:331 1.253
After features/support/hooks.rb:100 0.024
25.316
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.486
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.253
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the signing key used by the Upgrader is outdated 0.073
But a current signing key is available on our website 0.000
When the network is plugged 0.058
And Tor is ready 10.107
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.267
After features/support/hooks.rb:331 1.229
After features/support/hooks.rb:100 0.000