Project Number Date
test_Tails_ISO_devel 4636 25 Sep 2026, 12:15

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 10:52.295 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:3.379
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.099
And I create a 7200 MiB disk named "old" 0.031
And I plug USB drive "old" 1.041
And I write an old version of the Tails USB image to disk "old" 13.388
When I start Tails from USB drive "old" with network unplugged 46.550
Then the boot device has safe access rights 1.720
And Tails is running from USB drive "old" 0.195
And there is no persistence partition on USB drive "old" 0.036
And process "udev-watchdog" is running 0.041
And udev-watchdog is monitoring the correct device 0.161
And I unplug USB drive "old" 0.111
After features/support/hooks.rb:339 3.630
After features/support/hooks.rb:108 0.025
Tags: @product
1:17.014
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.077
And I start Tails from USB drive "old" with network unplugged and I login 46.051
Then Tails is running from USB drive "old" 0.248
And I create a persistent partition 21.970
And I take note of which tps features are available 5.656
Then a Tails persistence partition exists on USB drive "old" 0.416
And I shutdown Tails and wait for the computer to power off 2.592
After features/support/hooks.rb:339 0.284
After features/support/hooks.rb:108 0.005
Tags: @product
1:27.232
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.152
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.528
Then Tails is running from USB drive "old" 0.189
And all tps features are active 6.943
When I write some files expected to persist 1.008
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.122
And all persistence configuration files have safe access rights 0.247
And all persistent directories from the old Tails version have safe access rights 1.585
And I take note of which tps features are available 5.724
And I shutdown Tails and wait for the computer to power off 2.520
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 11.209
After features/support/hooks.rb:339 0.571
After features/support/hooks.rb:108 0.005
Tags: @product
2:10.220
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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 8.111
And I log in to a new session 10.305
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.822
And I plug USB drive "to_upgrade" 2.245
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.859
Then the running Tails is installed on USB drive "to_upgrade" 17.631
And I unplug USB drive "to_upgrade" 0.118
And I unplug USB drive "__internal" 0.126
After features/support/hooks.rb:339 1.458
After features/support/hooks.rb:108 0.000
Tags: @product
1:5.346
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.075
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.436
Then all tps features from the old Tails version are active 1.020
And Tails is running from USB drive "to_upgrade" 0.150
And the boot device has safe access rights 2.133
And the expected persistent files created with the old Tails version are present in the filesystem 0.924
And all persistent directories from the old Tails version have safe access rights 1.604
After features/support/hooks.rb:339 0.791
After features/support/hooks.rb:108 0.006
3:30.314
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.928
And no SquashFS delta is installed 0.055
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.215
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.141
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.271
When the network is plugged 0.024
And Tor is ready 12.654
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.490
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.038
Given I shutdown Tails and wait for the computer to power off 5.269
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.505
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.678
And the file system changes introduced in version 6.2~testoverlayfs are present 0.158
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.083
# 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.176
When the network is plugged 0.033
And Tor is ready 10.073
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.334
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.666
Given I shutdown Tails and wait for the computer to power off 2.625
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.878
Then Tails is running version 6.3~testoverlayfs 0.023
And all tps features are active 7.324
And the file system changes introduced in version 6.3~testoverlayfs are present 0.302
And only the 6.3~testoverlayfs SquashFS delta is installed 0.035
# 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.091
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.159
When the network is plugged 0.031
And Tor is ready 10.083
Then the Upgrader considers the system as up-to-date 10.388
# 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 3.141
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.326
After features/support/hooks.rb:339 0.964
After features/support/hooks.rb:108 0.009
18.787
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.918
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.060
And the signing key used by the Upgrader is outdated 0.039
But a current signing key is available on our website 0.000
When the network is plugged 0.027
And Tor is ready 8.037
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.454
After features/support/hooks.rb:339 0.941
After features/support/hooks.rb:108 0.000