Project Number Date
test_Tails_ISO_devel 4227 11 Feb 2026, 12:15

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 11:58.044 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:3.350
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.064
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 14.267
When I start Tails from USB drive "old" with network unplugged 44.594
Then the boot device has safe access rights 2.637
And Tails is running from USB drive "old" 0.315
And there is no persistence partition on USB drive "old" 0.040
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.198
And I unplug USB drive "old" 0.142
After features/support/hooks.rb:331 3.817
After features/support/hooks.rb:100 0.009
Tags: @product
1:28.526
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.059
And I start Tails from USB drive "old" with network unplugged and I login 53.299
Then Tails is running from USB drive "old" 0.264
And I create a persistent partition 25.333
And I take note of which tps features are available 0.789
Then a Tails persistence partition exists on USB drive "old" 0.630
And I shutdown Tails and wait for the computer to power off 8.148
After features/support/hooks.rb:331 0.343
After features/support/hooks.rb:100 0.006
Tags: @product
1:27.234
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.323
Then Tails is running from USB drive "old" 0.271
And all tps features are active 1.095
When I write some files expected to persist 1.305
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.137
And all persistence configuration files have safe access rights 0.312
And all persistent directories from the old Tails version have safe access rights 2.076
And I take note of which tps features are available 0.149
And I shutdown Tails and wait for the computer to power off 8.200
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.309
After features/support/hooks.rb:331 0.125
After features/support/hooks.rb:100 0.007
Tags: @product
2:27.532
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 without a persistent partition and stopped at Tails Greeter's login screen 21.684
And I log in to a new session 12.651
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.764
And I plug USB drive "to_upgrade" 2.236
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.620
Then the running Tails is installed on USB drive "to_upgrade" 16.228
And I unplug USB drive "to_upgrade" 0.160
And I unplug USB drive "__internal" 0.186
After features/support/hooks.rb:331 3.691
After features/support/hooks.rb:100 0.000
Tags: @product
1:16.207
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.092
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.691
Then all tps features from the old Tails version are active 1.016
And Tails is running from USB drive "to_upgrade" 0.550
And the boot device has safe access rights 2.557
And the expected persistent files created with the old Tails version are present in the filesystem 1.248
And all persistent directories from the old Tails version have safe access rights 2.050
After features/support/hooks.rb:331 0.667
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
3:55.048
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.027
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.825
And no SquashFS delta is installed 0.107
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.303
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.242
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.363
When the network is plugged 0.018
And Tor is ready 13.567
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.046
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.321
Given I shutdown Tails and wait for the computer to power off 11.479
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.129
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.170
And the file system changes introduced in version 6.2~testoverlayfs are present 0.222
And only the 6.2~testoverlayfs SquashFS delta is installed 0.045
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.171
# 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.272
When the network is plugged 0.017
And Tor is ready 9.941
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.967
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.800
Given I shutdown Tails and wait for the computer to power off 4.065
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.841
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.041
And the file system changes introduced in version 6.3~testoverlayfs are present 0.368
And only the 6.3~testoverlayfs SquashFS delta is installed 0.055
# 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.120
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.276
When the network is plugged 0.016
And Tor is ready 11.268
Then the Upgrader considers the system as up-to-date 10.587
# 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.880
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.433
After features/support/hooks.rb:331 1.014
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
20.144
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 7.775
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.213
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the signing key used by the Upgrader is outdated 0.057
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 10.112
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.926
After features/support/hooks.rb:331 0.750
After features/support/hooks.rb:100 0.000