Project Number Date
test_Tails_ISO_devel 4296 27 Mar 2026, 07:59

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:54.134 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:5.720
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.059
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 14.513
When I start Tails from USB drive "old" with network unplugged 46.537
Then the boot device has safe access rights 2.938
And Tails is running from USB drive "old" 0.223
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.036
And udev-watchdog is monitoring the correct device 0.187
And I unplug USB drive "old" 0.148
After features/support/hooks.rb:331 3.456
After features/support/hooks.rb:100 0.006
Tags: @product
1:29.903
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.048
And I start Tails from USB drive "old" with network unplugged and I login 55.515
Then Tails is running from USB drive "old" 0.263
And I create a persistent partition 24.610
And I take note of which tps features are available 0.733
Then a Tails persistence partition exists on USB drive "old" 0.685
And I shutdown Tails and wait for the computer to power off 8.047
After features/support/hooks.rb:331 0.491
After features/support/hooks.rb:100 0.007
Tags: @product
1:26.714
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.065
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.950
Then Tails is running from USB drive "old" 0.236
And all tps features are active 1.268
When I write some files expected to persist 1.398
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.159
And all persistence configuration files have safe access rights 0.443
And all persistent directories from the old Tails version have safe access rights 1.943
And I take note of which tps features are available 0.194
And I shutdown Tails and wait for the computer to power off 4.421
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.634
After features/support/hooks.rb:331 0.142
After features/support/hooks.rb:100 0.007
Tags: @product
2:24.160
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 8.171
And I log in to a new session 21.478
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.824
And I plug USB drive "to_upgrade" 2.295
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.401
Then the running Tails is installed on USB drive "to_upgrade" 17.632
And I unplug USB drive "to_upgrade" 0.158
And I unplug USB drive "__internal" 0.198
After features/support/hooks.rb:331 3.020
After features/support/hooks.rb:100 0.000
Tags: @product
1:13.338
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.058
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.478
Then all tps features from the old Tails version are active 1.158
And Tails is running from USB drive "to_upgrade" 0.268
And the boot device has safe access rights 2.910
And the expected persistent files created with the old Tails version are present in the filesystem 1.294
And all persistent directories from the old Tails version have safe access rights 2.169
After features/support/hooks.rb:331 1.001
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
4:44.978
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.719
And no SquashFS delta is installed 0.174
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.434
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.231
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.341
When the network is plugged 0.025
And Tor is ready 24.977
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.588
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.465
Given I shutdown Tails and wait for the computer to power off 21.198
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.508
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 1.252
And the file system changes introduced in version 6.2~testoverlayfs are present 0.243
And only the 6.2~testoverlayfs SquashFS delta is installed 0.045
# 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.259
When the network is plugged 0.021
And Tor is ready 20.751
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.068
Given I shutdown Tails and wait for the computer to power off 13.704
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.214
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.281
And the file system changes introduced in version 6.3~testoverlayfs are present 0.461
And only the 6.3~testoverlayfs SquashFS delta is installed 0.068
# 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.203
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.243
When the network is plugged 0.049
And Tor is ready 21.311
Then the Upgrader considers the system as up-to-date 0.114
# 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.980
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.386
After features/support/hooks.rb:331 1.026
After features/support/hooks.rb:100 0.025
Tags: @product @automatic_upgrade
29.318
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 7.765
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.297
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 0.041
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 20.688
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.449
After features/support/hooks.rb:331 0.952
After features/support/hooks.rb:100 0.000