Project Number Date
test_Tails_ISO_devel 3861 10 Jun 2025, 17:29

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 23:18.876 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
2:59.667
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.253
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.158
And I write an old version of the Tails USB image to disk "old" 59.389
When I start Tails from USB drive "old" with network unplugged 1:52.995
Then the boot device has safe access rights 4.324
And Tails is running from USB drive "old" 0.494
And there is no persistence partition on USB drive "old" 0.100
And process "udev-watchdog" is running 0.152
And udev-watchdog is monitoring the correct device 0.513
And I unplug USB drive "old" 0.235
After features/support/hooks.rb:330 4.070
After features/support/hooks.rb:100 0.032
Tags: @product
2:22.695
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.015
Given a computer 0.317
And I start Tails from USB drive "old" with network unplugged and I login 1:37.542
Then Tails is running from USB drive "old" 0.419
And I create a persistent partition 32.754
And I take note of which tps features are available 2.564
Then a Tails persistence partition exists on USB drive "old" 0.774
And I shutdown Tails and wait for the computer to power off 8.321
After features/support/hooks.rb:330 0.194
After features/support/hooks.rb:100 0.010
Tags: @product
3:31.852
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.204
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:40.263
Then Tails is running from USB drive "old" 0.929
And all tps features are active 4.154
When I write some files expected to persist 1.989
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.318
And all persistence configuration files have safe access rights 0.526
And all persistent directories from the old Tails version have safe access rights 3.107
And I take note of which tps features are available 0.562
And I shutdown Tails and wait for the computer to power off 6.534
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 33.262
After features/support/hooks.rb:330 0.187
After features/support/hooks.rb:100 0.011
Tags: @product
3:6.297
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 25.529
And I log in to a new session 24.026
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.841
And I plug USB drive "to_upgrade" 2.511
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:43.582
Then the running Tails is installed on USB drive "to_upgrade" 26.965
And I unplug USB drive "to_upgrade" 0.361
And I unplug USB drive "__internal" 0.479
After features/support/hooks.rb:330 3.089
After features/support/hooks.rb:100 0.000
Tags: @product
2:59.719
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Given a computer 0.271
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:47.317
Then all tps features from the old Tails version are active 1.869
And Tails is running from USB drive "to_upgrade" 0.346
And the boot device has safe access rights 5.046
And the expected persistent files created with the old Tails version are present in the filesystem 1.848
And all persistent directories from the old Tails version have safe access rights 3.019
After features/support/hooks.rb:330 1.218
After features/support/hooks.rb:100 0.027
7:40.129
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.540
And no SquashFS delta is installed 0.112
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.426
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.147
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.389
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.501
When the network is plugged 0.073
And Tor is ready 20.872
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.548
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.414
Given I shutdown Tails and wait for the computer to power off 11.330
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.352
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 8.725
And the file system changes introduced in version 6.2~testoverlayfs are present 0.322
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.280
# 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.397
When the network is plugged 0.434
And Tor is ready 21.324
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.511
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 12.158
Given I shutdown Tails and wait for the computer to power off 9.320
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:34.515
Then Tails is running version 6.3~testoverlayfs 0.026
And all tps features are active 2.987
And the file system changes introduced in version 6.3~testoverlayfs are present 0.702
And only the 6.3~testoverlayfs SquashFS delta is installed 0.131
# 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.458
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.395
When the network is plugged 0.077
And Tor is ready 21.038
Then the Upgrader considers the system as up-to-date 0.424
# 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 20.592
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.511
After features/support/hooks.rb:330 0.845
After features/support/hooks.rb:100 0.021
38.515
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.432
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.539
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.138
And the signing key used by the Upgrader is outdated 0.147
But a current signing key is available on our website 0.000
When the network is plugged 0.105
And Tor is ready 19.334
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.816
After features/support/hooks.rb:330 1.212
After features/support/hooks.rb:100 0.000