u-boot.git/lib/efi_selftest/Kconfig, branch master

efi_selftest: block device test requires CONFIG_DOS_PARTITION

2020-08-01T09:58:39+00:00

Do not execute the block device test if CONFIG_DOS_PARTITION=n.

Imply CONFIG_DOS_PARTITION in Kconfig.

Signed-off-by: Heinrich Schuchardt

efi_selftest: enable CONFIG_CMD_POWEROFF

2020-01-14T23:51:51+00:00

For automating testing we should be able to power off the test system.
The implementation of EFI_RESET_SHUTDOWN requires the do_poweroff()
function which is only available if CONFIG_CMD_POWEROFF=y.

Enable CONFIG_CMD_POWEROFF if PSCI reset is available.

Signed-off-by: Heinrich Schuchardt

efi_selftest: description of CMD_BOOTEFI_SELFTEST

2019-07-06T19:25:32+00:00

The current short description has a typo. Let it stand out clear that we
provide unit tests.

Improve the description of the CMD_BOOTEFI_SELFTEST configuration option.

Signed-off-by: Heinrich Schuchardt 
Reviewed-by: Alexander Graf

efi_selftest: building sandbox with EFI_SELFTEST

2018-12-02T20:59:37+00:00

Enable building the sandbox with CONFIG_EFI_SELFTEST.

Signed-off-by: Heinrich Schuchardt 
Signed-off-by: Alexander Graf

efi_loader: Disable efi selftest on sandbox for now

2018-09-23T19:55:31+00:00

The EFI selftest does not succeed on Sandbox yet. The network support
seems to need some love to actually make our current tests succeed.

So let's disable running the selftest on sandbox for now until "make
tests" just works. Then we can have more amazing CI than ever.

Signed-off-by: Alexander Graf

efi_selftest: imply FAT, FAT_WRITE

2018-06-03T13:27:21+00:00

efi_selftest_block_device accesses a FAT file system.

Signed-off-by: Heinrich Schuchardt 
Signed-off-by: Alexander Graf

efi_selftest: provide an EFI selftest application

2017-09-18T21:53:57+00:00

A testing framework for the EFI API is provided.
It can be executed with the 'bootefi selftest' command.

It is coded in a way that at a later stage we may turn it
into a standalone EFI application. The current build system
does not allow this yet.

All tests use a driver model and are run in three phases:
setup, execute, teardown.

A test may be setup and executed at boottime,
it may be setup at boottime and executed at runtime,
or it may be setup and executed at runtime.

After executing all tests the system is reset.

Signed-off-by: Heinrich Schuchardt 
Signed-off-by: Alexander Graf