Project Number Date
test_Tails_ISO_devel 4386 09 May 2026, 10:57

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:4.764 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:2.959
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.055
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 13.097
When I start Tails from USB drive "old" with network unplugged 45.539
Then the boot device has safe access rights 2.609
And Tails is running from USB drive "old" 0.207
And there is no persistence partition on USB drive "old" 0.045
And process "udev-watchdog" is running 0.044
And udev-watchdog is monitoring the correct device 0.167
And I unplug USB drive "old" 0.167
After features/support/hooks.rb:331 1.157
After features/support/hooks.rb:100 0.006
Tags: @product
1:26.866
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.048
And I start Tails from USB drive "old" with network unplugged and I login 52.609
Then Tails is running from USB drive "old" 0.229
And I create a persistent partition 24.740
And I take note of which tps features are available 0.780
Then a Tails persistence partition exists on USB drive "old" 0.585
And I shutdown Tails and wait for the computer to power off 7.872
After features/support/hooks.rb:331 0.464
After features/support/hooks.rb:100 0.007
Tags: @product
1:25.185
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.639
Then Tails is running from USB drive "old" 0.226
And all tps features are active 1.113
When I write some files expected to persist 1.279
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.155
And all persistence configuration files have safe access rights 0.418
And all persistent directories from the old Tails version have safe access rights 1.872
And I take note of which tps features are available 0.179
And I shutdown Tails and wait for the computer to power off 8.199
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.050
After features/support/hooks.rb:331 0.171
After features/support/hooks.rb:100 0.006
Tags: @product
2:9.190
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 without a persistent partition and stopped at Tails Greeter's login screen 7.804
And I log in to a new session 11.843
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.770
And I plug USB drive "to_upgrade" 2.239
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.631
Then the running Tails is installed on USB drive "to_upgrade" 15.582
And I unplug USB drive "to_upgrade" 0.157
And I unplug USB drive "__internal" 0.160
After features/support/hooks.rb:331 1.902
After features/support/hooks.rb:100 0.000
Tags: @product
1:6.719
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.052
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.358
Then all tps features from the old Tails version are active 0.942
And Tails is running from USB drive "to_upgrade" 0.208
And the boot device has safe access rights 2.378
And the expected persistent files created with the old Tails version are present in the filesystem 0.997
And all persistent directories from the old Tails version have safe access rights 1.780
After features/support/hooks.rb:331 0.509
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
4:29.675
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.230
And no SquashFS delta is installed 0.070
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.231
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.246
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.361
When the network is plugged 0.014
And Tor is ready 19.187
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.351
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.446
Given I shutdown Tails and wait for the computer to power off 19.743
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.368
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.032
And the file system changes introduced in version 6.2~testoverlayfs are present 0.255
And only the 6.2~testoverlayfs SquashFS delta is installed 0.039
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.125
# 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.242
When the network is plugged 0.015
And Tor is ready 20.422
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.352
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.877
Given I shutdown Tails and wait for the computer to power off 17.183
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.659
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.120
And the file system changes introduced in version 6.3~testoverlayfs are present 0.454
And only the 6.3~testoverlayfs SquashFS delta is installed 0.038
# 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.115
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.193
When the network is plugged 0.019
And Tor is ready 22.367
Then the Upgrader considers the system as up-to-date 0.110
# 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.304
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.428
After features/support/hooks.rb:331 0.817
After features/support/hooks.rb:100 0.026
Tags: @product @automatic_upgrade
24.168
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.251
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.293
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 0.076
But a current signing key is available on our website 0.000
When the network is plugged 0.049
And Tor is ready 16.092
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.353
After features/support/hooks.rb:331 0.553
After features/support/hooks.rb:100 0.000