Project Number Date
test_Tails_ISO_21318-tor-browser-16.0 32 05 Jul 2026, 08:10

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 11:41.049 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:14.709
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.048
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.178
When I start Tails from USB drive "old" with network unplugged 57.209
Then the boot device has safe access rights 2.621
And Tails is running from USB drive "old" 0.226
And there is no persistence partition on USB drive "old" 0.035
And process "udev-watchdog" is running 0.060
And udev-watchdog is monitoring the correct device 0.176
And I unplug USB drive "old" 0.129
After features/support/hooks.rb:339 3.853
After features/support/hooks.rb:108 0.029
Tags: @product
1:27.913
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.042
And I start Tails from USB drive "old" with network unplugged and I login 52.196
Then Tails is running from USB drive "old" 0.251
And I create a persistent partition 23.445
And I take note of which tps features are available 3.644
Then a Tails persistence partition exists on USB drive "old" 0.470
And I shutdown Tails and wait for the computer to power off 7.861
After features/support/hooks.rb:339 0.497
After features/support/hooks.rb:108 0.006
Tags: @product
1:32.821
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.748
Then Tails is running from USB drive "old" 0.228
And all tps features are active 4.770
When I write some files expected to persist 1.126
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.177
And all persistence configuration files have safe access rights 0.279
And all persistent directories from the old Tails version have safe access rights 1.625
And I take note of which tps features are available 3.567
And I shutdown Tails and wait for the computer to power off 7.836
# 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.408
After features/support/hooks.rb:339 0.472
After features/support/hooks.rb:108 0.006
Tags: @product
2:8.534
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 7.954
And I log in to a new session 11.599
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.771
And I plug USB drive "to_upgrade" 2.229
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.120
Then the running Tails is installed on USB drive "to_upgrade" 14.611
And I unplug USB drive "to_upgrade" 0.118
And I unplug USB drive "__internal" 0.129
After features/support/hooks.rb:339 2.140
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.972
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.054
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.659
Then all tps features from the old Tails version are active 0.865
And Tails is running from USB drive "to_upgrade" 0.282
And the boot device has safe access rights 2.196
And the expected persistent files created with the old Tails version are present in the filesystem 1.045
And all persistent directories from the old Tails version have safe access rights 1.869
After features/support/hooks.rb:339 0.811
After features/support/hooks.rb:108 0.005
3:48.563
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 8.077
And no SquashFS delta is installed 0.067
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.199
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.188
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.365
When the network is plugged 0.014
And Tor is ready 13.176
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.975
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.625
Given I shutdown Tails and wait for the computer to power off 10.787
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.075
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.927
And the file system changes introduced in version 6.2~testoverlayfs are present 0.241
And only the 6.2~testoverlayfs SquashFS delta is installed 0.078
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.148
# 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.199
When the network is plugged 0.012
And Tor is ready 10.972
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.522
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.846
Given I shutdown Tails and wait for the computer to power off 7.831
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.758
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 4.663
And the file system changes introduced in version 6.3~testoverlayfs are present 0.364
And only the 6.3~testoverlayfs SquashFS delta is installed 0.043
# 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.188
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.193
When the network is plugged 0.016
And Tor is ready 9.875
Then the Upgrader considers the system as up-to-date 10.529
# 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.197
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.341
After features/support/hooks.rb:339 0.852
After features/support/hooks.rb:108 0.010
18.535
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.422
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.210
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.044
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 9.140
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.646
After features/support/hooks.rb:339 0.703
After features/support/hooks.rb:108 0.000