Project Number Date
test_Tails_ISO_stable 6046 08 Jan 2026, 19:21

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:15.301 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:15.612
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.063
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.035
And I write an old version of the Tails USB image to disk "old" 14.272
When I start Tails from USB drive "old" with network unplugged 56.258
Then the boot device has safe access rights 3.061
And Tails is running from USB drive "old" 0.239
And there is no persistence partition on USB drive "old" 0.053
And process "udev-watchdog" is running 0.102
And udev-watchdog is monitoring the correct device 0.284
And I unplug USB drive "old" 0.231
After features/support/hooks.rb:331 3.817
After features/support/hooks.rb:100 0.012
Tags: @product
1:36.318
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.015
Given a computer 0.094
And I start Tails from USB drive "old" with network unplugged and I login 1:1.667
Then Tails is running from USB drive "old" 0.480
And I create a persistent partition 24.128
And I take note of which tps features are available 0.766
Then a Tails persistence partition exists on USB drive "old" 0.672
And I shutdown Tails and wait for the computer to power off 8.508
After features/support/hooks.rb:331 0.764
After features/support/hooks.rb:100 0.012
Tags: @product
1:33.719
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.128
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.480
Then Tails is running from USB drive "old" 0.551
And all tps features are active 1.322
When I write some files expected to persist 1.449
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.173
And all persistence configuration files have safe access rights 0.311
And all persistent directories from the old Tails version have safe access rights 1.972
And I take note of which tps features are available 0.164
And I shutdown Tails and wait for the computer to power off 8.550
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.614
After features/support/hooks.rb:331 0.127
After features/support/hooks.rb:100 0.009
Tags: @product
2:16.981
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 8.957
And I log in to a new session 13.931
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.031
And I plug USB drive "to_upgrade" 2.371
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.697
Then the running Tails is installed on USB drive "to_upgrade" 17.706
And I unplug USB drive "to_upgrade" 0.149
And I unplug USB drive "__internal" 0.135
After features/support/hooks.rb:331 3.654
After features/support/hooks.rb:100 0.000
Tags: @product
1:14.179
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.173
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.686
Then all tps features from the old Tails version are active 1.231
And Tails is running from USB drive "to_upgrade" 0.283
And the boot device has safe access rights 3.172
And the expected persistent files created with the old Tails version are present in the filesystem 1.398
And all persistent directories from the old Tails version have safe access rights 2.234
After features/support/hooks.rb:331 0.646
After features/support/hooks.rb:100 0.027
Tags: @product @automatic_upgrade
3:56.396
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 8.160
And no SquashFS delta is installed 0.084
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.333
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.229
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.404
When the network is plugged 0.039
And Tor is ready 15.949
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.411
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.238
Given I shutdown Tails and wait for the computer to power off 9.886
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.585
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 1.746
And the file system changes introduced in version 6.2~testoverlayfs are present 0.346
And only the 6.2~testoverlayfs SquashFS delta is installed 0.063
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.160
# 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.250
When the network is plugged 0.086
And Tor is ready 11.462
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.625
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.070
Given I shutdown Tails and wait for the computer to power off 8.475
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.995
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.294
And the file system changes introduced in version 6.3~testoverlayfs are present 0.469
And only the 6.3~testoverlayfs SquashFS delta is installed 0.059
# 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.134
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.236
When the network is plugged 0.022
And Tor is ready 11.555
Then the Upgrader considers the system as up-to-date 10.582
# 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.888
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.464
After features/support/hooks.rb:331 1.049
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
22.094
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 with a persistent partition enabled and logged in 8.283
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.507
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.075
And the signing key used by the Upgrader is outdated 0.096
But a current signing key is available on our website 0.000
When the network is plugged 0.157
And Tor is ready 10.976
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.996
After features/support/hooks.rb:331 0.684
After features/support/hooks.rb:100 0.000