Project Number Date
test_Tails_ISO_21603-fragnesia 1 14 May 2026, 19:24

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:53.944 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:4.266
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.078
And I create a 7200 MiB disk named "old" 0.012
And I plug USB drive "old" 1.025
And I write an old version of the Tails USB image to disk "old" 14.190
When I start Tails from USB drive "old" with network unplugged 44.926
Then the boot device has safe access rights 3.310
And Tails is running from USB drive "old" 0.228
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.173
And I unplug USB drive "old" 0.188
After features/support/hooks.rb:335 1.429
After features/support/hooks.rb:104 0.006
Tags: @product
1:32.236
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.055
And I start Tails from USB drive "old" with network unplugged and I login 57.305
Then Tails is running from USB drive "old" 0.387
And I create a persistent partition 26.425
And I take note of which tps features are available 0.495
Then a Tails persistence partition exists on USB drive "old" 0.691
And I shutdown Tails and wait for the computer to power off 6.874
After features/support/hooks.rb:335 0.145
After features/support/hooks.rb:104 0.007
Tags: @product
1:32.407
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.075
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.789
Then Tails is running from USB drive "old" 0.430
And all tps features are active 1.375
When I write some files expected to persist 1.427
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.213
And all persistence configuration files have safe access rights 0.391
And all persistent directories from the old Tails version have safe access rights 2.251
And I take note of which tps features are available 0.144
And I shutdown Tails and wait for the computer to power off 8.437
# 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.871
After features/support/hooks.rb:335 0.502
After features/support/hooks.rb:104 0.007
Tags: @product
2:13.845
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 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.328
And I log in to a new session 14.357
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.728
And I plug USB drive "to_upgrade" 2.231
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.622
Then the running Tails is installed on USB drive "to_upgrade" 16.290
And I unplug USB drive "to_upgrade" 0.144
And I unplug USB drive "__internal" 0.142
After features/support/hooks.rb:335 2.399
After features/support/hooks.rb:104 0.000
Tags: @product
1:14.810
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.090
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.244
Then all tps features from the old Tails version are active 1.176
And Tails is running from USB drive "to_upgrade" 0.270
And the boot device has safe access rights 2.702
And the expected persistent files created with the old Tails version are present in the filesystem 1.254
And all persistent directories from the old Tails version have safe access rights 2.071
After features/support/hooks.rb:335 1.298
After features/support/hooks.rb:104 0.009
Tags: @product @automatic_upgrade
3:55.421
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.831
And no SquashFS delta is installed 0.092
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.244
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.243
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.410
When the network is plugged 0.014
And Tor is ready 12.635
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.594
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.860
Given I shutdown Tails and wait for the computer to power off 9.758
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.711
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.110
And the file system changes introduced in version 6.2~testoverlayfs are present 0.211
And only the 6.2~testoverlayfs SquashFS delta is installed 0.055
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.137
# 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.198
When the network is plugged 0.014
And Tor is ready 11.897
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.903
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.054
Given I shutdown Tails and wait for the computer to power off 8.285
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.931
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.363
And the file system changes introduced in version 6.3~testoverlayfs are present 0.374
And only the 6.3~testoverlayfs SquashFS delta is installed 0.049
# 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.143
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.233
When the network is plugged 0.015
And Tor is ready 10.593
Then the Upgrader considers the system as up-to-date 10.500
# 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.382
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.513
After features/support/hooks.rb:335 1.055
After features/support/hooks.rb:104 0.011
Tags: @product @automatic_upgrade
20.957
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.776
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.234
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
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.016
And Tor is ready 10.080
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.756
After features/support/hooks.rb:335 0.816
After features/support/hooks.rb:104 0.000