Project Number Date
test_Tails_ISO_21681-dont-create-tilde-directory-in-home 1 14 Jul 2026, 19:37

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:38.188 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.862
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.047
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 13.106
When I start Tails from USB drive "old" with network unplugged 57.445
Then the boot device has safe access rights 2.603
And Tails is running from USB drive "old" 0.217
And there is no persistence partition on USB drive "old" 0.051
And process "udev-watchdog" is running 0.065
And udev-watchdog is monitoring the correct device 0.177
And I unplug USB drive "old" 0.125
After features/support/hooks.rb:339 3.751
After features/support/hooks.rb:108 0.072
Tags: @product
1:31.198
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.073
And I start Tails from USB drive "old" with network unplugged and I login 53.478
Then Tails is running from USB drive "old" 0.233
And I create a persistent partition 24.809
And I take note of which tps features are available 3.988
Then a Tails persistence partition exists on USB drive "old" 0.520
And I shutdown Tails and wait for the computer to power off 8.093
After features/support/hooks.rb:339 0.138
After features/support/hooks.rb:108 0.006
Tags: @product
1:30.513
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.048
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.196
Then Tails is running from USB drive "old" 0.262
And all tps features are active 4.805
When I write some files expected to persist 1.370
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.191
And all persistence configuration files have safe access rights 0.323
And all persistent directories from the old Tails version have safe access rights 1.825
And I take note of which tps features are available 3.631
And I shutdown Tails and wait for the computer to power off 3.940
# 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.918
After features/support/hooks.rb:339 0.300
After features/support/hooks.rb:108 0.006
Tags: @product
2:8.490
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 7.934
And I log in to a new session 11.634
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.791
And I plug USB drive "to_upgrade" 2.237
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.284
Then the running Tails is installed on USB drive "to_upgrade" 14.352
And I unplug USB drive "to_upgrade" 0.127
And I unplug USB drive "__internal" 0.127
After features/support/hooks.rb:339 1.993
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.627
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.070
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.697
Then all tps features from the old Tails version are active 0.923
And Tails is running from USB drive "to_upgrade" 0.239
And the boot device has safe access rights 2.703
And the expected persistent files created with the old Tails version are present in the filesystem 1.112
And all persistent directories from the old Tails version have safe access rights 1.880
After features/support/hooks.rb:339 0.661
After features/support/hooks.rb:108 0.030
Tags: @product @automatic_upgrade
3:41.898
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.852
And no SquashFS delta is installed 0.053
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.174
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.201
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.329
When the network is plugged 0.018
And Tor is ready 13.008
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.061
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.310
Given I shutdown Tails and wait for the computer to power off 9.379
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.604
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.572
And the file system changes introduced in version 6.2~testoverlayfs are present 0.213
And only the 6.2~testoverlayfs SquashFS delta is installed 0.040
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.144
# 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.248
When the network is plugged 0.018
And Tor is ready 9.866
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.007
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.162
Given I shutdown Tails and wait for the computer to power off 2.679
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.201
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 5.264
And the file system changes introduced in version 6.3~testoverlayfs are present 0.358
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.131
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.184
When the network is plugged 0.012
And Tor is ready 9.922
Then the Upgrader considers the system as up-to-date 10.522
# 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.791
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.461
After features/support/hooks.rb:339 1.083
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
20.597
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.164
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.218
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.075
And the signing key used by the Upgrader is outdated 0.063
But a current signing key is available on our website 0.003
When the network is plugged 0.021
And Tor is ready 9.845
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.205
After features/support/hooks.rb:339 0.570
After features/support/hooks.rb:108 0.000