Project Number Date
test_Tails_ISO_21681-dont-create-tilde-directory-in-home 2 15 Jul 2026, 09:08

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:33.895 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:13.190
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.068
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 14.263
When I start Tails from USB drive "old" with network unplugged 53.469
Then the boot device has safe access rights 3.460
And Tails is running from USB drive "old" 0.333
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.074
And udev-watchdog is monitoring the correct device 0.271
And I unplug USB drive "old" 0.155
After features/support/hooks.rb:339 3.667
After features/support/hooks.rb:108 0.007
Tags: @product
1:36.565
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.069
And I start Tails from USB drive "old" with network unplugged and I login 58.179
Then Tails is running from USB drive "old" 0.233
And I create a persistent partition 24.831
And I take note of which tps features are available 4.439
Then a Tails persistence partition exists on USB drive "old" 0.532
And I shutdown Tails and wait for the computer to power off 8.278
After features/support/hooks.rb:339 0.306
After features/support/hooks.rb:108 0.008
Tags: @product
1:43.274
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.114
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:10.214
Then Tails is running from USB drive "old" 0.274
And all tps features are active 5.874
When I write some files expected to persist 1.625
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.273
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.335
And I take note of which tps features are available 4.593
And I shutdown Tails and wait for the computer to power off 4.248
# 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" 13.372
After features/support/hooks.rb:339 0.547
After features/support/hooks.rb:108 0.006
Tags: @product
2:15.271
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.143
And I log in to a new session 15.699
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.764
And I plug USB drive "to_upgrade" 2.222
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.675
Then the running Tails is installed on USB drive "to_upgrade" 15.480
And I unplug USB drive "to_upgrade" 0.136
And I unplug USB drive "__internal" 0.149
After features/support/hooks.rb:339 2.326
After features/support/hooks.rb:108 0.000
Tags: @product
1:20.422
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.068
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:12.183
Then all tps features from the old Tails version are active 1.157
And Tails is running from USB drive "to_upgrade" 0.535
And the boot device has safe access rights 2.901
And the expected persistent files created with the old Tails version are present in the filesystem 1.303
And all persistent directories from the old Tails version have safe access rights 2.271
After features/support/hooks.rb:339 0.912
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
4:3.515
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 8.352
And no SquashFS delta is installed 0.085
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.265
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.306
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.430
When the network is plugged 0.042
And Tor is ready 13.894
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.286
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.047
Given I shutdown Tails and wait for the computer to power off 7.177
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.153
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 6.403
And the file system changes introduced in version 6.2~testoverlayfs are present 0.205
And only the 6.2~testoverlayfs SquashFS delta is installed 0.049
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.151
# 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.218
When the network is plugged 0.020
And Tor is ready 10.375
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.566
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.954
Given I shutdown Tails and wait for the computer to power off 4.226
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.688
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 6.935
And the file system changes introduced in version 6.3~testoverlayfs are present 0.498
And only the 6.3~testoverlayfs SquashFS delta is installed 0.055
# 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.184
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.266
When the network is plugged 0.019
And Tor is ready 10.208
Then the Upgrader considers the system as up-to-date 10.686
# 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.315
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.373
After features/support/hooks.rb:339 0.922
After features/support/hooks.rb:108 0.014
Tags: @product @automatic_upgrade
21.654
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.688
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.263
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the signing key used by the Upgrader is outdated 0.119
But a current signing key is available on our website 0.000
When the network is plugged 0.050
And Tor is ready 10.950
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.523
After features/support/hooks.rb:339 0.553
After features/support/hooks.rb:108 0.000