Project Number Date
test_Tails_ISO_devel 4519 29 Jul 2026, 21:40

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:59.334 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.668
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.049
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 14.071
When I start Tails from USB drive "old" with network unplugged 44.872
Then the boot device has safe access rights 2.923
And Tails is running from USB drive "old" 0.233
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.235
And I unplug USB drive "old" 0.133
After features/support/hooks.rb:339 1.489
After features/support/hooks.rb:108 0.007
Tags: @product
1:31.138
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.008
Given a computer 0.077
And I start Tails from USB drive "old" with network unplugged and I login 56.117
Then Tails is running from USB drive "old" 0.223
And I create a persistent partition 25.573
And I take note of which tps features are available 4.314
Then a Tails persistence partition exists on USB drive "old" 0.590
And I shutdown Tails and wait for the computer to power off 4.241
After features/support/hooks.rb:339 0.265
After features/support/hooks.rb:108 0.007
Tags: @product
1:37.118
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.064
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.713
Then Tails is running from USB drive "old" 0.241
And all tps features are active 5.460
When I write some files expected to persist 1.281
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.157
And all persistence configuration files have safe access rights 0.354
And all persistent directories from the old Tails version have safe access rights 2.117
And I take note of which tps features are available 4.002
And I shutdown Tails and wait for the computer to power off 4.071
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 12.652
After features/support/hooks.rb:339 0.246
After features/support/hooks.rb:108 0.006
Tags: @product
2:12.251
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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 8.037
And I log in to a new session 12.276
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.841
And I plug USB drive "to_upgrade" 2.263
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.504
Then the running Tails is installed on USB drive "to_upgrade" 15.969
And I unplug USB drive "to_upgrade" 0.181
And I unplug USB drive "__internal" 0.177
After features/support/hooks.rb:339 0.667
After features/support/hooks.rb:108 0.000
Tags: @product
1:16.747
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given a computer 0.107
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:9.672
Then all tps features from the old Tails version are active 0.980
And Tails is running from USB drive "to_upgrade" 0.233
And the boot device has safe access rights 2.473
And the expected persistent files created with the old Tails version are present in the filesystem 1.296
And all persistent directories from the old Tails version have safe access rights 1.984
After features/support/hooks.rb:339 1.150
After features/support/hooks.rb:108 0.043
Tags: @product @automatic_upgrade
3:57.098
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.014
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.158
And no SquashFS delta is installed 0.073
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.214
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.247
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.393
When the network is plugged 0.019
And Tor is ready 14.547
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.618
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.888
Given I shutdown Tails and wait for the computer to power off 6.798
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.831
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 4.914
And the file system changes introduced in version 6.2~testoverlayfs are present 0.210
And only the 6.2~testoverlayfs SquashFS delta is installed 0.041
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.128
# 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.196
When the network is plugged 0.014
And Tor is ready 10.346
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.292
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.493
Given I shutdown Tails and wait for the computer to power off 4.172
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.326
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 5.534
And the file system changes introduced in version 6.3~testoverlayfs are present 0.373
And only the 6.3~testoverlayfs SquashFS delta is installed 0.042
# 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.129
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.217
When the network is plugged 0.013
And Tor is ready 10.563
Then the Upgrader considers the system as up-to-date 10.583
# 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.259
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.365
After features/support/hooks.rb:339 0.888
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
21.311
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.804
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.077
And the signing key used by the Upgrader is outdated 0.091
But a current signing key is available on our website 0.000
When the network is plugged 0.019
And Tor is ready 9.735
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.369
After features/support/hooks.rb:339 1.011
After features/support/hooks.rb:108 0.000