Project Number Date
test_Tails_ISO_stable 6058 13 Jan 2026, 22:42

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 12:6.481 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:17.202
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.118
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 13.589
When I start Tails from USB drive "old" with network unplugged 58.479
Then the boot device has safe access rights 3.272
And Tails is running from USB drive "old" 0.274
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.169
And I unplug USB drive "old" 0.172
After features/support/hooks.rb:331 3.419
After features/support/hooks.rb:100 0.053
Tags: @product
1:28.065
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login 53.745
Then Tails is running from USB drive "old" 0.325
And I create a persistent partition 24.520
And I take note of which tps features are available 0.673
Then a Tails persistence partition exists on USB drive "old" 0.614
And I shutdown Tails and wait for the computer to power off 8.135
After features/support/hooks.rb:331 0.275
After features/support/hooks.rb:100 0.007
Tags: @product
1:27.870
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.055
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.531
Then Tails is running from USB drive "old" 0.252
And all tps features are active 1.148
When I write some files expected to persist 1.322
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.262
And all persistence configuration files have safe access rights 0.387
And all persistent directories from the old Tails version have safe access rights 2.302
And I take note of which tps features are available 0.188
And I shutdown Tails and wait for the computer to power off 8.247
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.171
After features/support/hooks.rb:331 0.446
After features/support/hooks.rb:100 0.007
Tags: @product
2:13.760
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 8.970
And I log in to a new session 11.828
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.888
And I plug USB drive "to_upgrade" 2.338
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.898
Then the running Tails is installed on USB drive "to_upgrade" 16.553
And I unplug USB drive "to_upgrade" 0.144
And I unplug USB drive "__internal" 0.138
After features/support/hooks.rb:331 7.094
After features/support/hooks.rb:100 0.000
Tags: @product
1:9.407
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.070
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.390
Then all tps features from the old Tails version are active 1.048
And Tails is running from USB drive "to_upgrade" 0.262
And the boot device has safe access rights 2.599
And the expected persistent files created with the old Tails version are present in the filesystem 1.098
And all persistent directories from the old Tails version have safe access rights 1.938
After features/support/hooks.rb:331 0.810
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:8.947
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.061
And no SquashFS delta is installed 0.222
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.188
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.195
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.331
When the network is plugged 0.015
And Tor is ready 42.925
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.378
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.774
Given I shutdown Tails and wait for the computer to power off 9.449
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.281
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.296
And the file system changes introduced in version 6.2~testoverlayfs are present 0.223
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.124
# 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.259
When the network is plugged 0.015
And Tor is ready 10.557
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.582
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.154
Given I shutdown Tails and wait for the computer to power off 8.183
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.813
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.168
And the file system changes introduced in version 6.3~testoverlayfs are present 0.364
And only the 6.3~testoverlayfs SquashFS delta is installed 0.044
# 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.139
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.213
When the network is plugged 0.023
And Tor is ready 11.650
Then the Upgrader considers the system as up-to-date 10.538
# 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 4.265
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.370
After features/support/hooks.rb:331 1.060
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
21.227
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.898
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.237
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.043
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 10.311
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.667
After features/support/hooks.rb:331 1.028
After features/support/hooks.rb:100 0.000