Project Number Date
test_Tails_ISO_devel 4310 01 Apr 2026, 12:53

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 13:45.643 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:19.448
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.052
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 15.001
When I start Tails from USB drive "old" with network unplugged 59.776
Then the boot device has safe access rights 2.893
And Tails is running from USB drive "old" 0.268
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.054
And udev-watchdog is monitoring the correct device 0.197
And I unplug USB drive "old" 0.132
After features/support/hooks.rb:331 1.286
After features/support/hooks.rb:100 0.007
Tags: @product
1:33.522
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.058
And I start Tails from USB drive "old" with network unplugged and I login 57.099
Then Tails is running from USB drive "old" 0.272
And I create a persistent partition 26.046
And I take note of which tps features are available 0.779
Then a Tails persistence partition exists on USB drive "old" 0.644
And I shutdown Tails and wait for the computer to power off 8.621
After features/support/hooks.rb:331 0.493
After features/support/hooks.rb:100 0.005
Tags: @product
1:29.735
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.109
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.985
Then Tails is running from USB drive "old" 0.298
And all tps features are active 1.156
When I write some files expected to persist 1.400
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.216
And all persistence configuration files have safe access rights 0.446
And all persistent directories from the old Tails version have safe access rights 2.097
And I take note of which tps features are available 0.154
And I shutdown Tails and wait for the computer to power off 4.415
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.454
After features/support/hooks.rb:331 0.578
After features/support/hooks.rb:100 0.007
Tags: @product
2:22.412
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 9.110
And I log in to a new session 19.893
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.925
And I plug USB drive "to_upgrade" 2.230
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.598
Then the running Tails is installed on USB drive "to_upgrade" 17.306
And I unplug USB drive "to_upgrade" 0.186
And I unplug USB drive "__internal" 0.161
After features/support/hooks.rb:331 3.271
After features/support/hooks.rb:100 0.000
Tags: @product
1:21.098
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.060
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:13.501
Then all tps features from the old Tails version are active 1.023
And Tails is running from USB drive "to_upgrade" 0.239
And the boot device has safe access rights 2.733
And the expected persistent files created with the old Tails version are present in the filesystem 1.237
And all persistent directories from the old Tails version have safe access rights 2.303
After features/support/hooks.rb:331 0.733
After features/support/hooks.rb:100 0.008
5:10.507
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 with a persistent partition enabled and logged in 8.623
And no SquashFS delta is installed 0.069
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.249
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.214
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.350
When the network is plugged 0.019
And Tor is ready 45.493
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.626
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.925
Given I shutdown Tails and wait for the computer to power off 19.695
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.737
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 1.271
And the file system changes introduced in version 6.2~testoverlayfs are present 0.344
And only the 6.2~testoverlayfs SquashFS delta is installed 0.054
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.149
# 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.246
When the network is plugged 0.014
And Tor is ready 20.297
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.462
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.162
Given I shutdown Tails and wait for the computer to power off 17.739
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.371
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.374
And the file system changes introduced in version 6.3~testoverlayfs are present 0.408
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.159
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.283
When the network is plugged 0.014
And Tor is ready 20.564
Then the Upgrader considers the system as up-to-date 0.121
# 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.907
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.424
After features/support/hooks.rb:331 1.105
After features/support/hooks.rb:100 0.013
28.919
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.786
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.272
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the signing key used by the Upgrader is outdated 0.080
But a current signing key is available on our website 0.000
When the network is plugged 0.023
And Tor is ready 20.298
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.408
After features/support/hooks.rb:331 0.880
After features/support/hooks.rb:100 0.000