Project Number Date
test_Tails_ISO_devel 4496 15 Jul 2026, 11:28

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:34.218 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:12.374
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.194
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.818
When I start Tails from USB drive "old" with network unplugged 53.501
Then the boot device has safe access rights 3.104
And Tails is running from USB drive "old" 0.237
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.079
And udev-watchdog is monitoring the correct device 0.214
And I unplug USB drive "old" 0.137
After features/support/hooks.rb:339 3.758
After features/support/hooks.rb:108 0.007
Tags: @product
1:38.196
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login 57.710
Then Tails is running from USB drive "old" 0.260
And I create a persistent partition 26.748
And I take note of which tps features are available 4.505
Then a Tails persistence partition exists on USB drive "old" 0.646
And I shutdown Tails and wait for the computer to power off 8.272
After features/support/hooks.rb:339 0.148
After features/support/hooks.rb:108 0.006
Tags: @product
1:42.044
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.054
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:10.580
Then Tails is running from USB drive "old" 0.345
And all tps features are active 5.846
When I write some files expected to persist 1.348
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.193
And all persistence configuration files have safe access rights 0.325
And all persistent directories from the old Tails version have safe access rights 1.891
And I take note of which tps features are available 4.441
And I shutdown Tails and wait for the computer to power off 4.263
# 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.753
After features/support/hooks.rb:339 0.331
After features/support/hooks.rb:108 0.023
Tags: @product
2:13.133
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.481
And I log in to a new session 12.942
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.774
And I plug USB drive "to_upgrade" 2.249
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.133
Then the running Tails is installed on USB drive "to_upgrade" 16.291
And I unplug USB drive "to_upgrade" 0.132
And I unplug USB drive "__internal" 0.128
After features/support/hooks.rb:339 2.104
After features/support/hooks.rb:108 0.000
Tags: @product
1:16.476
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.058
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.408
Then all tps features from the old Tails version are active 1.089
And Tails is running from USB drive "to_upgrade" 0.282
And the boot device has safe access rights 3.137
And the expected persistent files created with the old Tails version are present in the filesystem 1.175
And all persistent directories from the old Tails version have safe access rights 2.325
After features/support/hooks.rb:339 0.819
After features/support/hooks.rb:108 0.017
Tags: @product @automatic_upgrade
4:10.601
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 8.111
And no SquashFS delta is installed 0.089
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.228
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.290
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.433
When the network is plugged 0.030
And Tor is ready 12.613
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.223
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.063
Given I shutdown Tails and wait for the computer to power off 9.887
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.691
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 5.481
And the file system changes introduced in version 6.2~testoverlayfs are present 0.249
And only the 6.2~testoverlayfs SquashFS delta is installed 0.056
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.176
# 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.190
When the network is plugged 0.020
And Tor is ready 10.929
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.417
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.989
Given I shutdown Tails and wait for the computer to power off 8.485
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.593
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 5.559
And the file system changes introduced in version 6.3~testoverlayfs are present 0.362
And only the 6.3~testoverlayfs SquashFS delta is installed 0.047
# 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.189
When the network is plugged 0.014
And Tor is ready 11.458
Then the Upgrader considers the system as up-to-date 10.647
# 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.328
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.538
After features/support/hooks.rb:339 1.166
After features/support/hooks.rb:108 0.047
Tags: @product @automatic_upgrade
21.390
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.692
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.343
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 0.052
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 10.165
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.058
After features/support/hooks.rb:339 0.857
After features/support/hooks.rb:108 0.000