Project Number Date
test_Tails_ISO_devel 4380 07 May 2026, 07:30

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:13.475 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:8.508
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.054
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.079
When I start Tails from USB drive "old" with network unplugged 51.202
Then the boot device has safe access rights 2.510
And Tails is running from USB drive "old" 0.194
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.046
And udev-watchdog is monitoring the correct device 0.194
And I unplug USB drive "old" 0.156
After features/support/hooks.rb:331 1.332
After features/support/hooks.rb:100 0.006
Tags: @product
1:23.679
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.055
And I start Tails from USB drive "old" with network unplugged and I login 50.903
Then Tails is running from USB drive "old" 0.228
And I create a persistent partition 23.350
And I take note of which tps features are available 0.607
Then a Tails persistence partition exists on USB drive "old" 0.548
And I shutdown Tails and wait for the computer to power off 7.985
After features/support/hooks.rb:331 0.241
After features/support/hooks.rb:100 0.007
Tags: @product
1:24.639
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.049
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.355
Then Tails is running from USB drive "old" 0.216
And all tps features are active 1.159
When I write some files expected to persist 1.285
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.195
And all persistence configuration files have safe access rights 0.385
And all persistent directories from the old Tails version have safe access rights 1.770
And I take note of which tps features are available 0.151
And I shutdown Tails and wait for the computer to power off 8.121
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.950
After features/support/hooks.rb:331 0.192
After features/support/hooks.rb:100 0.007
Tags: @product
2:10.735
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 7.812
And I log in to a new session 12.291
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.694
And I plug USB drive "to_upgrade" 2.219
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.579
Then the running Tails is installed on USB drive "to_upgrade" 15.841
And I unplug USB drive "to_upgrade" 0.159
And I unplug USB drive "__internal" 0.136
After features/support/hooks.rb:331 3.563
After features/support/hooks.rb:100 0.000
Tags: @product
1:7.602
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.090
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.736
Then all tps features from the old Tails version are active 1.015
And Tails is running from USB drive "to_upgrade" 0.245
And the boot device has safe access rights 2.551
And the expected persistent files created with the old Tails version are present in the filesystem 1.111
And all persistent directories from the old Tails version have safe access rights 1.851
After features/support/hooks.rb:331 0.670
After features/support/hooks.rb:100 0.005
4:32.227
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 7.941
And no SquashFS delta is installed 0.077
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.195
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.209
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.365
When the network is plugged 0.020
And Tor is ready 20.830
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.465
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.306
Given I shutdown Tails and wait for the computer to power off 19.896
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.533
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 0.978
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.047
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.131
# 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.208
When the network is plugged 0.016
And Tor is ready 20.556
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.347
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.013
Given I shutdown Tails and wait for the computer to power off 18.555
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.236
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.119
And the file system changes introduced in version 6.3~testoverlayfs are present 0.383
And only the 6.3~testoverlayfs SquashFS delta is installed 0.043
# 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.133
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.208
When the network is plugged 0.014
And Tor is ready 20.294
Then the Upgrader considers the system as up-to-date 0.097
# 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.358
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.376
After features/support/hooks.rb:331 0.755
After features/support/hooks.rb:100 0.011
26.081
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 7.500
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.200
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.048
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 17.903
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.370
After features/support/hooks.rb:331 0.692
After features/support/hooks.rb:100 0.000