Project Number Date
test_Tails_ISO_fix-bad-comments 1 01 Jul 2026, 13:58

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:14.761 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:25.170
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.061
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.023
And I write an old version of the Tails USB image to disk "old" 13.694
When I start Tails from USB drive "old" with network unplugged 1:6.726
Then the boot device has safe access rights 2.906
And Tails is running from USB drive "old" 0.286
And there is no persistence partition on USB drive "old" 0.057
And process "udev-watchdog" is running 0.055
And udev-watchdog is monitoring the correct device 0.213
And I unplug USB drive "old" 0.135
After features/support/hooks.rb:339 3.666
After features/support/hooks.rb:108 0.008
Tags: @product
1:30.882
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.062
And I start Tails from USB drive "old" with network unplugged and I login 53.736
Then Tails is running from USB drive "old" 0.218
And I create a persistent partition 24.069
And I take note of which tps features are available 4.213
Then a Tails persistence partition exists on USB drive "old" 0.582
And I shutdown Tails and wait for the computer to power off 8.000
After features/support/hooks.rb:339 0.519
After features/support/hooks.rb:108 0.008
Tags: @product
1:35.701
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.050
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.563
Then Tails is running from USB drive "old" 0.258
And all tps features are active 4.774
When I write some files expected to persist 1.194
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.221
And all persistence configuration files have safe access rights 0.322
And all persistent directories from the old Tails version have safe access rights 1.850
And I take note of which tps features are available 3.753
And I shutdown Tails and wait for the computer to power off 8.268
# 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.442
After features/support/hooks.rb:339 0.178
After features/support/hooks.rb:108 0.006
Tags: @product
2:11.730
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.823
And I log in to a new session 12.866
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.766
And I plug USB drive "to_upgrade" 2.224
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.266
Then the running Tails is installed on USB drive "to_upgrade" 15.396
And I unplug USB drive "to_upgrade" 0.215
And I unplug USB drive "__internal" 0.171
After features/support/hooks.rb:339 2.351
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.461
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.071
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.615
Then all tps features from the old Tails version are active 1.011
And Tails is running from USB drive "to_upgrade" 0.229
And the boot device has safe access rights 2.562
And the expected persistent files created with the old Tails version are present in the filesystem 1.013
And all persistent directories from the old Tails version have safe access rights 1.958
After features/support/hooks.rb:339 0.786
After features/support/hooks.rb:108 0.007
3:58.357
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.367
And no SquashFS delta is installed 0.057
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.250
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.247
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.362
When the network is plugged 0.022
And Tor is ready 13.308
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.764
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.420
Given I shutdown Tails and wait for the computer to power off 9.546
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.269
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 5.211
And the file system changes introduced in version 6.2~testoverlayfs are present 0.202
And only the 6.2~testoverlayfs SquashFS delta is installed 0.044
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.143
# 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.200
When the network is plugged 0.015
And Tor is ready 10.401
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.223
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.157
Given I shutdown Tails and wait for the computer to power off 2.737
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.865
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 5.420
And the file system changes introduced in version 6.3~testoverlayfs are present 0.348
And only the 6.3~testoverlayfs SquashFS delta is installed 0.060
# 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.164
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.253
When the network is plugged 0.018
And Tor is ready 11.004
Then the Upgrader considers the system as up-to-date 10.617
# 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.238
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.322
After features/support/hooks.rb:339 1.044
After features/support/hooks.rb:108 0.013
20.458
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.483
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.242
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.065
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 9.937
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.661
After features/support/hooks.rb:339 0.803
After features/support/hooks.rb:108 0.000