Project Number Date
test_Tails_ISO_remove-boum.org 1 09 Sep 2026, 18:59

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:15.163 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:20.024
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.096
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.023
And I write an old version of the Tails USB image to disk "old" 14.195
When I start Tails from USB drive "old" with network unplugged 1:1.453
Then the boot device has safe access rights 2.552
And Tails is running from USB drive "old" 0.220
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.043
And udev-watchdog is monitoring the correct device 0.228
And I unplug USB drive "old" 0.116
After features/support/hooks.rb:339 1.229
After features/support/hooks.rb:108 0.005
Tags: @product
1:30.631
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.123
And I start Tails from USB drive "old" with network unplugged and I login 52.337
Then Tails is running from USB drive "old" 0.218
And I create a persistent partition 25.471
And I take note of which tps features are available 7.515
Then a Tails persistence partition exists on USB drive "old" 0.614
And I shutdown Tails and wait for the computer to power off 4.349
After features/support/hooks.rb:339 0.207
After features/support/hooks.rb:108 0.006
Tags: @product
1:40.445
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.079
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.635
Then Tails is running from USB drive "old" 0.218
And all tps features are active 8.464
When I write some files expected to persist 1.285
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.178
And all persistence configuration files have safe access rights 0.297
And all persistent directories from the old Tails version have safe access rights 1.919
And I take note of which tps features are available 6.558
And I shutdown Tails and wait for the computer to power off 4.208
# 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.599
After features/support/hooks.rb:339 0.361
After features/support/hooks.rb:108 0.007
Tags: @product
2:14.499
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 without a persistent partition and stopped at Tails Greeter's login screen 8.679
And I log in to a new session 12.446
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.685
And I plug USB drive "to_upgrade" 2.206
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.439
Then the running Tails is installed on USB drive "to_upgrade" 18.792
And I unplug USB drive "to_upgrade" 0.137
And I unplug USB drive "__internal" 0.111
After features/support/hooks.rb:339 1.914
After features/support/hooks.rb:108 0.000
Tags: @product
1:13.216
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.084
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.128
Then all tps features from the old Tails version are active 1.181
And Tails is running from USB drive "to_upgrade" 0.288
And the boot device has safe access rights 2.413
And the expected persistent files created with the old Tails version are present in the filesystem 1.044
And all persistent directories from the old Tails version have safe access rights 2.074
After features/support/hooks.rb:339 1.302
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:42.766
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.898
And no SquashFS delta is installed 0.064
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.236
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.248
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.292
When the network is plugged 0.030
And Tor is ready 12.638
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.101
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.355
Given I shutdown Tails and wait for the computer to power off 5.331
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.214
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.442
And the file system changes introduced in version 6.2~testoverlayfs are present 0.187
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.123
# 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.161
When the network is plugged 0.036
And Tor is ready 11.320
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.431
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.490
Given I shutdown Tails and wait for the computer to power off 2.790
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.694
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 9.082
And the file system changes introduced in version 6.3~testoverlayfs are present 0.312
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.100
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.209
When the network is plugged 0.031
And Tor is ready 10.454
Then the Upgrader considers the system as up-to-date 0.135
# 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.759
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.434
After features/support/hooks.rb:339 0.644
After features/support/hooks.rb:108 0.022
Tags: @product @automatic_upgrade
33.579
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 21.704
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.291
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the signing key used by the Upgrader is outdated 0.059
But a current signing key is available on our website 0.000
When the network is plugged 0.031
And Tor is ready 9.924
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.521
After features/support/hooks.rb:339 0.939
After features/support/hooks.rb:108 0.000