Project Number Date
test_Tails_ISO_devel 4189 25 Jan 2026, 12:14

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:1.285 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:16.804
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.055
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.925
When I start Tails from USB drive "old" with network unplugged 58.041
Then the boot device has safe access rights 3.070
And Tails is running from USB drive "old" 0.293
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.042
And udev-watchdog is monitoring the correct device 0.176
And I unplug USB drive "old" 0.133
After features/support/hooks.rb:331 3.833
After features/support/hooks.rb:100 0.046
Tags: @product
1:25.704
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.062
And I start Tails from USB drive "old" with network unplugged and I login 52.804
Then Tails is running from USB drive "old" 0.247
And I create a persistent partition 24.583
And I take note of which tps features are available 0.725
Then a Tails persistence partition exists on USB drive "old" 0.575
And I shutdown Tails and wait for the computer to power off 6.705
After features/support/hooks.rb:331 0.151
After features/support/hooks.rb:100 0.006
Tags: @product
1:24.850
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.418
Then Tails is running from USB drive "old" 0.248
And all tps features are active 1.163
When I write some files expected to persist 1.323
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.214
And all persistence configuration files have safe access rights 0.316
And all persistent directories from the old Tails version have safe access rights 1.980
And I take note of which tps features are available 0.240
And I shutdown Tails and wait for the computer to power off 4.360
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.533
After features/support/hooks.rb:331 0.530
After features/support/hooks.rb:100 0.022
Tags: @product
2:16.351
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.559
And I log in to a new session 10.725
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.866
And I plug USB drive "to_upgrade" 2.233
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.520
Then the running Tails is installed on USB drive "to_upgrade" 17.170
And I unplug USB drive "to_upgrade" 0.139
And I unplug USB drive "__internal" 0.136
After features/support/hooks.rb:331 4.120
After features/support/hooks.rb:100 0.000
Tags: @product
1:16.795
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.082
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:9.330
Then all tps features from the old Tails version are active 1.097
And Tails is running from USB drive "to_upgrade" 0.234
And the boot device has safe access rights 2.814
And the expected persistent files created with the old Tails version are present in the filesystem 1.097
And all persistent directories from the old Tails version have safe access rights 2.137
After features/support/hooks.rb:331 0.467
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
3:59.591
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.468
And no SquashFS delta is installed 0.097
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.232
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
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.374
When the network is plugged 0.018
And Tor is ready 15.053
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.779
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.081
Given I shutdown Tails and wait for the computer to power off 17.292
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.522
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.272
And the file system changes introduced in version 6.2~testoverlayfs are present 0.247
And only the 6.2~testoverlayfs SquashFS delta is installed 0.052
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.139
# 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.238
When the network is plugged 0.018
And Tor is ready 10.544
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.011
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.140
Given I shutdown Tails and wait for the computer to power off 8.312
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.270
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.318
And the file system changes introduced in version 6.3~testoverlayfs are present 0.389
And only the 6.3~testoverlayfs SquashFS delta is installed 0.064
# 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.141
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.190
When the network is plugged 0.016
And Tor is ready 10.959
Then the Upgrader considers the system as up-to-date 10.501
# 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.147
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.373
After features/support/hooks.rb:331 0.692
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
21.188
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.127
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.268
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
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.018
And Tor is ready 10.861
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.813
After features/support/hooks.rb:331 1.060
After features/support/hooks.rb:100 0.000