Project Number Date
test_Tails_ISO_21472-circumvention-settings-2 6 01 Apr 2026, 02:12

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:18.963 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:18.946
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.051
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 13.163
When I start Tails from USB drive "old" with network unplugged 1:1.347
Then the boot device has safe access rights 2.728
And Tails is running from USB drive "old" 0.201
And there is no persistence partition on USB drive "old" 0.035
And process "udev-watchdog" is running 0.063
And udev-watchdog is monitoring the correct device 0.188
And I unplug USB drive "old" 0.143
After features/support/hooks.rb:331 3.898
After features/support/hooks.rb:100 0.006
Tags: @product
1:24.462
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.047
And I start Tails from USB drive "old" with network unplugged and I login 51.754
Then Tails is running from USB drive "old" 0.237
And I create a persistent partition 23.033
And I take note of which tps features are available 0.708
Then a Tails persistence partition exists on USB drive "old" 0.536
And I shutdown Tails and wait for the computer to power off 8.144
After features/support/hooks.rb:331 0.385
After features/support/hooks.rb:100 0.007
Tags: @product
1:18.991
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.060
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.848
Then Tails is running from USB drive "old" 0.249
And all tps features are active 1.136
When I write some files expected to persist 1.277
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.215
And all persistence configuration files have safe access rights 0.430
And all persistent directories from the old Tails version have safe access rights 1.909
And I take note of which tps features are available 0.149
And I shutdown Tails and wait for the computer to power off 4.044
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.668
After features/support/hooks.rb:331 0.368
After features/support/hooks.rb:100 0.006
Tags: @product
2:10.573
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.654
And I log in to a new session 12.221
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.740
And I plug USB drive "to_upgrade" 2.228
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.332
Then the running Tails is installed on USB drive "to_upgrade" 15.117
And I unplug USB drive "to_upgrade" 0.128
And I unplug USB drive "__internal" 0.148
After features/support/hooks.rb:331 2.181
After features/support/hooks.rb:100 0.000
Tags: @product
1:6.505
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:0.143
Then all tps features from the old Tails version are active 0.976
And Tails is running from USB drive "to_upgrade" 0.236
And the boot device has safe access rights 2.379
And the expected persistent files created with the old Tails version are present in the filesystem 0.974
And all persistent directories from the old Tails version have safe access rights 1.748
After features/support/hooks.rb:331 0.765
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:34.728
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.866
And no SquashFS delta is installed 0.076
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.233
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.221
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.328
When the network is plugged 0.018
And Tor is ready 22.087
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.351
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.627
Given I shutdown Tails and wait for the computer to power off 19.818
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.655
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.135
And the file system changes introduced in version 6.2~testoverlayfs are present 0.209
And only the 6.2~testoverlayfs SquashFS delta is installed 0.051
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.139
# 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.217
When the network is plugged 0.017
And Tor is ready 21.069
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.406
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.156
Given I shutdown Tails and wait for the computer to power off 18.411
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.510
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 1.252
And the file system changes introduced in version 6.3~testoverlayfs are present 0.352
And only the 6.3~testoverlayfs SquashFS delta is installed 0.050
# 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.131
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.222
When the network is plugged 0.026
And Tor is ready 21.178
Then the Upgrader considers the system as up-to-date 0.122
# 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.327
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.393
After features/support/hooks.rb:331 0.792
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
24.755
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 7.443
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.269
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
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.018
And Tor is ready 16.561
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.381
After features/support/hooks.rb:331 0.971
After features/support/hooks.rb:100 0.000