Project Number Date
test_Tails_ISO_21318-tor-browser-16.0 46 17 Jul 2026, 08:18

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:22.633 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.161
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.064
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 14.038
When I start Tails from USB drive "old" with network unplugged 52.051
Then the boot device has safe access rights 3.178
And Tails is running from USB drive "old" 0.293
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.212
And I unplug USB drive "old" 0.130
After features/support/hooks.rb:339 1.516
After features/support/hooks.rb:108 0.006
Tags: @product
1:34.092
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.061
And I start Tails from USB drive "old" with network unplugged and I login 54.728
Then Tails is running from USB drive "old" 0.225
And I create a persistent partition 25.397
And I take note of which tps features are available 4.702
Then a Tails persistence partition exists on USB drive "old" 0.617
And I shutdown Tails and wait for the computer to power off 8.360
After features/support/hooks.rb:339 0.274
After features/support/hooks.rb:108 0.007
Tags: @product
1:38.975
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given a computer 0.072
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:8.429
Then Tails is running from USB drive "old" 0.235
And all tps features are active 5.299
When I write some files expected to persist 1.305
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.222
And all persistence configuration files have safe access rights 0.347
And all persistent directories from the old Tails version have safe access rights 2.037
And I take note of which tps features are available 4.111
And I shutdown Tails and wait for the computer to power off 4.427
# 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" 12.485
After features/support/hooks.rb:339 0.394
After features/support/hooks.rb:108 0.006
Tags: @product
2:13.572
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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.368
And I log in to a new session 12.613
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.844
And I plug USB drive "to_upgrade" 2.362
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.259
Then the running Tails is installed on USB drive "to_upgrade" 16.838
And I unplug USB drive "to_upgrade" 0.149
And I unplug USB drive "__internal" 0.135
After features/support/hooks.rb:339 1.972
After features/support/hooks.rb:108 0.000
Tags: @product
1:16.888
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.064
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:9.329
Then all tps features from the old Tails version are active 1.132
And Tails is running from USB drive "to_upgrade" 0.273
And the boot device has safe access rights 2.927
And the expected persistent files created with the old Tails version are present in the filesystem 1.200
And all persistent directories from the old Tails version have safe access rights 1.960
After features/support/hooks.rb:339 0.886
After features/support/hooks.rb:108 0.034
4:6.649
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.885
And no SquashFS delta is installed 0.063
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.251
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.240
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.406
When the network is plugged 0.014
And Tor is ready 12.736
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.285
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.143
Given I shutdown Tails and wait for the computer to power off 9.619
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.101
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 5.811
And the file system changes introduced in version 6.2~testoverlayfs are present 0.263
And only the 6.2~testoverlayfs SquashFS delta is installed 0.048
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.175
# 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.240
When the network is plugged 0.028
And Tor is ready 9.963
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.397
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.755
Given I shutdown Tails and wait for the computer to power off 8.400
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.118
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 6.086
And the file system changes introduced in version 6.3~testoverlayfs are present 0.354
And only the 6.3~testoverlayfs SquashFS delta is installed 0.048
# 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.132
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.211
When the network is plugged 0.013
And Tor is ready 10.522
Then the Upgrader considers the system as up-to-date 10.597
# 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.274
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.378
After features/support/hooks.rb:339 0.799
After features/support/hooks.rb:108 0.022
21.293
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.847
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.274
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.047
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 10.321
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.733
After features/support/hooks.rb:339 0.926
After features/support/hooks.rb:108 0.000