Project Number Date
test_Tails_ISO_devel 4317 04 Apr 2026, 08:06

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:3.262 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:11.880
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.047
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.013
And I write an old version of the Tails USB image to disk "old" 13.578
When I start Tails from USB drive "old" with network unplugged 53.777
Then the boot device has safe access rights 2.763
And Tails is running from USB drive "old" 0.224
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.051
And udev-watchdog is monitoring the correct device 0.226
And I unplug USB drive "old" 0.147
After features/support/hooks.rb:331 1.248
After features/support/hooks.rb:100 0.006
Tags: @product
1:25.724
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.054
And I start Tails from USB drive "old" with network unplugged and I login 52.084
Then Tails is running from USB drive "old" 0.308
And I create a persistent partition 24.223
And I take note of which tps features are available 0.667
Then a Tails persistence partition exists on USB drive "old" 0.535
And I shutdown Tails and wait for the computer to power off 7.850
After features/support/hooks.rb:331 0.176
After features/support/hooks.rb:100 0.007
Tags: @product
1:35.950
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 1:10.688
Then Tails is running from USB drive "old" 0.247
And all tps features are active 1.160
When I write some files expected to persist 1.211
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.154
And all persistence configuration files have safe access rights 0.460
And all persistent directories from the old Tails version have safe access rights 1.803
And I take note of which tps features are available 0.149
And I shutdown Tails and wait for the computer to power off 7.876
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.149
After features/support/hooks.rb:331 0.475
After features/support/hooks.rb:100 0.007
Tags: @product
2:21.525
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.535
And I log in to a new session 19.441
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.795
And I plug USB drive "to_upgrade" 2.216
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.352
Then the running Tails is installed on USB drive "to_upgrade" 17.906
And I unplug USB drive "to_upgrade" 0.125
And I unplug USB drive "__internal" 0.152
After features/support/hooks.rb:331 3.623
After features/support/hooks.rb:100 0.000
Tags: @product
1:8.777
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.046
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.085
Then all tps features from the old Tails version are active 1.091
And Tails is running from USB drive "to_upgrade" 0.281
And the boot device has safe access rights 2.364
And the expected persistent files created with the old Tails version are present in the filesystem 1.085
And all persistent directories from the old Tails version have safe access rights 1.822
After features/support/hooks.rb:331 0.933
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:50.667
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 8.273
And no SquashFS delta is installed 0.079
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.397
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.202
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.345
When the network is plugged 0.014
And Tor is ready 35.411
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.352
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.021
Given I shutdown Tails and wait for the computer to power off 25.168
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.416
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.064
And the file system changes introduced in version 6.2~testoverlayfs are present 0.201
And only the 6.2~testoverlayfs SquashFS delta is installed 0.043
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.129
# 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.187
When the network is plugged 0.016
And Tor is ready 20.335
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.371
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.049
Given I shutdown Tails and wait for the computer to power off 17.232
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.037
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 0.995
And the file system changes introduced in version 6.3~testoverlayfs are present 0.310
And only the 6.3~testoverlayfs SquashFS delta is installed 0.040
# 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.130
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.226
When the network is plugged 0.022
And Tor is ready 20.906
Then the Upgrader considers the system as up-to-date 0.096
# 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.175
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.342
After features/support/hooks.rb:331 0.851
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
28.736
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.612
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.283
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the signing key used by the Upgrader is outdated 0.046
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 20.337
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.392
After features/support/hooks.rb:331 1.173
After features/support/hooks.rb:100 0.000