\r
## Basic Status\r
\r
-| Package | Windows VS2019 (IA32/X64)| Ubuntu GCC (IA32/X64/ARM/AARCH64) | Known Issues |\r
-| :---- | :----- | :---- | :--- |\r
-| ArmPkg |\r
-| ArmPlatformPkg |\r
-| ArmVirtPkg | SEE PACKAGE README | SEE PACKAGE README |\r
-| CryptoPkg | :heavy_check_mark: | :heavy_check_mark: | Spell checking in audit mode\r
-| DynamicTablesPkg |\r
-| EmbeddedPkg |\r
-| EmulatorPkg | SEE PACKAGE README | SEE PACKAGE README | Spell checking in audit mode\r
-| FatPkg | :heavy_check_mark: | :heavy_check_mark: |\r
-| FmpDevicePkg | :heavy_check_mark: | :heavy_check_mark: |\r
-| IntelFsp2Pkg |\r
-| IntelFsp2WrapperPkg |\r
-| MdeModulePkg | :heavy_check_mark: | :heavy_check_mark: | DxeIpl dependency on ArmPkg, Depends on StandaloneMmPkg, Spell checking in audit mode\r
-| MdePkg | :heavy_check_mark: | :heavy_check_mark: | Spell checking in audit mode\r
-| NetworkPkg | :heavy_check_mark: | :heavy_check_mark: | Spell checking in audit mode\r
-| OvmfPkg | SEE PACKAGE README | SEE PACKAGE README | Spell checking in audit mode\r
-| PcAtChipsetPkg | :heavy_check_mark: | :heavy_check_mark: |\r
-| SecurityPkg | :heavy_check_mark: | :heavy_check_mark: | Spell checking in audit mode\r
-| ShellPkg | :heavy_check_mark: | :heavy_check_mark: | Spell checking in audit mode, 3 modules are not being built by DSC\r
-| SignedCapsulePkg |\r
-| SourceLevelDebugPkg |\r
-| StandaloneMmPkg |\r
-| UefiCpuPkg | :heavy_check_mark: | :heavy_check_mark: | Spell checking in audit mode, 2 binary modules not being built by DSC\r
-| UefiPayloadPkg |\r
+| Package | Windows VS2019 (IA32/X64)| Ubuntu GCC (IA32/X64/ARM/AARCH64) | Known Issues |\r
+| :---- | :----- | :---- | :--- |\r
+| ArmPkg |\r
+| ArmPlatformPkg |\r
+| ArmVirtPkg | SEE PACKAGE README | SEE PACKAGE README |\r
+| CryptoPkg | :heavy_check_mark: | :heavy_check_mark: | Spell checking in audit mode\r
+| DynamicTablesPkg |\r
+| EmbeddedPkg |\r
+| EmulatorPkg | SEE PACKAGE README | SEE PACKAGE README | Spell checking in audit mode\r
+| FatPkg | :heavy_check_mark: | :heavy_check_mark: |\r
+| FmpDevicePkg | :heavy_check_mark: | :heavy_check_mark: |\r
+| IntelFsp2Pkg |\r
+| IntelFsp2WrapperPkg |\r
+| MdeModulePkg | :heavy_check_mark: | :heavy_check_mark: | DxeIpl dependency on ArmPkg, Depends on StandaloneMmPkg, Spell checking in audit mode\r
+| MdePkg | :heavy_check_mark: | :heavy_check_mark: | Spell checking in audit mode\r
+| NetworkPkg | :heavy_check_mark: | :heavy_check_mark: | Spell checking in audit mode\r
+| OvmfPkg | SEE PACKAGE README | SEE PACKAGE README | Spell checking in audit mode\r
+| PcAtChipsetPkg | :heavy_check_mark: | :heavy_check_mark: |\r
+| SecurityPkg | :heavy_check_mark: | :heavy_check_mark: | Spell checking in audit mode\r
+| ShellPkg | :heavy_check_mark: | :heavy_check_mark: | Spell checking in audit mode, 3 modules are not being built by DSC\r
+| SignedCapsulePkg |\r
+| SourceLevelDebugPkg |\r
+| StandaloneMmPkg |\r
+| UefiCpuPkg | :heavy_check_mark: | :heavy_check_mark: | Spell checking in audit mode, 2 binary modules not being built by DSC\r
+| UefiPayloadPkg |\r
+| UnitTestFrameworkPkg | :heavy_check_mark: | :heavy_check_mark: |\r
\r
For more detailed status look at the test results of the latest CI run on the\r
repo readme.\r
* VS 2017 or VS 2019\r
* Windows SDK (for rc)\r
* Windows WDK (for capsules)\r
- * Ubuntu 16.04\r
+ * Ubuntu 18.04 or Fedora\r
* GCC5\r
* Easy to add more but this is the current state\r
2. Python 3.7.x or newer on path\r
\r
### Module Inclusion Test - DscCompleteCheck\r
\r
-This test scans all available modules (via INF files) and compares them to the\r
-package-level DSC file for the package each module is contained within. The test\r
-considers it an error if any module does not appear in the `Components` section\r
-of at least one package-level DSC (indicating that it would not be built if the\r
-package were built).\r
+This scans all INF files from a package and confirms they are\r
+listed in the package level DSC file. The test considers it an error if any INF\r
+does not appear in the `Components` section of the package-level DSC (indicating\r
+that it would not be built if the package were built). This is critical because\r
+much of the CI infrastructure assumes that all modules will be listed in the DSC\r
+and compiled.\r
+\r
+This test will ignore INFs in the following cases:\r
+\r
+1. When `MODULE_TYPE` = `HOST_APPLICATION`\r
+2. When a Library instance **only** supports the `HOST_APPLICATION` environment\r
+\r
+### Host Module Inclusion Test - HostUnitTestDscCompleteCheck\r
+\r
+This test scans all INF files from a package for those related to host\r
+based unit tests and confirms they are listed in the unit test DSC file for the package.\r
+The test considers it an error if any INF meeting the requirements does not appear\r
+in the `Components` section of the unit test DSC. This is critical because\r
+much of the CI infrastructure assumes that modules will be listed in the DSC\r
+and compiled.\r
+\r
+This test will only require INFs in the following cases:\r
+\r
+1. When `MODULE_TYPE` = `HOST_APPLICATION`\r
+2. When a Library instance explicitly supports the `HOST_APPLICATION` environment\r
\r
### Code Compilation Test - CompilerPlugin\r
\r
and builds every package-level DSC on every toolchain and for every architecture\r
that is supported. Any module that fails to build is considered an error.\r
\r
+### Host Unit Test Compilation and Run Test - HostUnitTestCompilerPlugin\r
+\r
+A test that compiles the dsc for host based unit test apps.\r
+On Windows this will also enable a build plugin to execute that will run the unit tests and verify the results.\r
+\r
+These tools will be invoked on any CI\r
+pass that includes the NOOPT target. In order for these tools to do their job,\r
+the package and tests must be configured in a particular way...\r
+\r
+#### Including Host-Based Tests in the Package YAML\r
+\r
+For example, looking at the `MdeModulePkg.ci.yaml` config file, there are two\r
+config options that control HostBased test behavior:\r
+\r
+```json\r
+ ## options defined .pytool/Plugin/HostUnitTestCompilerPlugin\r
+ "HostUnitTestCompilerPlugin": {\r
+ "DscPath": "Test/MdeModulePkgHostTest.dsc"\r
+ },\r
+```\r
+\r
+This option tell the test builder to run. The test builder needs to know which\r
+modules in this package are host-based tests, so that DSC path is provided.\r
+\r
+#### Configuring the HostBased DSC\r
+\r
+The HostBased DSC for `MdeModulePkg` is located at\r
+`MdeModulePkg/Test/MdeModulePkgHostTest.dsc`.\r
+\r
+To add automated host-based unit test building to a new package, create a\r
+similar DSC. The new DSC should make sure to have the `NOOPT` BUILD_TARGET\r
+and should include the line:\r
+\r
+```\r
+!include UnitTestFrameworkPkg/UnitTestFrameworkPkgHost.dsc.inc\r
+```\r
+\r
+All of the modules that are included in the `Components` section of this\r
+DSC should be of type HOST_APPLICATION.\r
+\r
### GUID Uniqueness Test - GuidCheck\r
\r
This test works on the collection of all packages rather than an individual\r
| global-nix | edk2_invocable++ | Running on Linux based OS |\r
| edk2-build | | This indicates that an invocable is building EDK2 based UEFI code |\r
| cibuild | set in .pytool/CISettings.py | Suggested target for edk2 continuous integration builds. Tools used for CiBuilds can use this scope. Example: asl compiler |\r
+| host-based-test | set in .pytool/CISettings.py | Turns on the host based tests and plugin |\r
+| host-test-win | set in .pytool/CISettings.py | Enables the host based test runner for Windows |\r
\r
## Future investments\r
\r
packages. As long as your DSC file knows where to find the lib implementation that you want to use,\r
you should be good to go.\r
\r
-See this example in 'SampleUnitTestApp.inf'...\r
+See this example in 'SampleUnitTestUefiShell.inf'...\r
\r
```\r
[Packages]\r
PrintLib\r
```\r
\r
+Also, if you want you test to automatically be picked up by the Test Runner plugin, you will need\r
+to make sure that the module `BASE_NAME` contains the word `Test`...\r
+\r
+```\r
+[Defines]\r
+ BASE_NAME = SampleUnitTestUefiShell\r
+```\r
+\r
### Requirements - Code\r
\r
Not to state the obvious, but let's make sure we have the following include before getting too far along...\r
\r
## Development\r
\r
-When using the EDK2 Pytools for CI testing, the host-based unit tests will be built and run on any build that includes the `NOOPT` build target.\r
+When using the EDK2 Pytools for CI testing, the host-based unit tests will be built and run on any build that includes\r
+the `NOOPT` build target.\r
\r
-If you are trying to iterate on a single test, a convenient pattern is to build only that test module. For example, the following command will build only the SafeIntLib host-based test from the MdePkg...\r
+If you are trying to iterate on a single test, a convenient pattern is to build only that test module. For example,\r
+the following command will build only the SafeIntLib host-based test from the MdePkg...\r
\r
```bash\r
stuart_ci_build -c .pytool/CISettings.py TOOL_CHAIN_TAG=VS2017 -p MdePkg -t NOOPT BUILDMODULE=MdePkg/Test/UnitTest/Library/BaseSafeIntLib/TestBaseSafeIntLib.inf\r
\r
We will continue trying to make these as similar as possible.\r
\r
+## Unit Test Location/Layout Rules\r
+\r
+Code/Test | Location\r
+--------- | --------\r
+Host-Based Unit Tests for a Library/Protocol/PPI/GUID Interface | If what's being tested is an interface (e.g. a library with a public header file, like DebugLib), the test should be scoped to the parent package.<br/>Example: `MdePkg/Test/UnitTest/[Library/Protocol/Ppi/Guid]/`<br/><br/>A real-world example of this is the BaseSafeIntLib test in MdePkg.<br/>`MdePkg/Test/UnitTest/Library/BaseSafeIntLib/TestBaseSafeIntLibHost.inf`\r
+Host-Based Unit Tests for a Library/Driver (PEI/DXE/SMM) implementation | If what's being tested is a specific implementation (e.g. BaseDebugLibSerialPort for DebugLib), the test should be scoped to the implementation directory itself, in a UnitTest subdirectory.<br/><br/>Module Example: `MdeModulePkg/Universal/EsrtFmpDxe/UnitTest/`<br/>Library Example: `MdePkg/Library/BaseMemoryLib/UnitTest/`\r
+Host-Based Tests for a Functionality or Feature | If you're writing a functional test that operates at the module level (i.e. if it's more than a single file or library), the test should be located in the package-level Tests directory under the HostFuncTest subdirectory.<br/>For example, if you were writing a test for the entire FMP Device Framework, you might put your test in:<br/>`FmpDevicePkg/Test/HostFuncTest/FmpDeviceFramework`<br/><br/>If the feature spans multiple packages, it's location should be determined by the package owners related to the feature.\r
+Non-Host-Based (PEI/DXE/SMM/Shell) Tests for a Functionality or Feature | Similar to Host-Based, if the feature is in one package, should be located in the `*Pkg/Test/[Shell/Dxe/Smm/Pei]Test` directory.<br/><br/>If the feature spans multiple packages, it's location should be determined by the package owners related to the feature.<br/><br/>USAGE EXAMPLES<br/>PEI Example: MP_SERVICE_PPI. Or check MTRR configuration in a notification function.<br/> SMM Example: a test in a protocol callback function. (It is different with the solution that SmmAgent+ShellApp)<br/>DXE Example: a test in a UEFI event call back to check SPI/SMRAM status. <br/> Shell Example: the SMM handler audit test has a shell-based app that interacts with an SMM handler to get information. The SMM paging audit test gathers information about both DXE and SMM. And the SMM paging functional test actually forces errors into SMM via a DXE driver.\r
+\r
+### Example Directory Tree\r
+\r
+```text\r
+<PackageName>Pkg/\r
+ ComponentY/\r
+ ComponentY.inf\r
+ ComponentY.c\r
+ UnitTest/\r
+ ComponentYHostUnitTest.inf # Host-Based Test for Driver Module\r
+ ComponentYUnitTest.c\r
+\r
+ Library/\r
+ GeneralPurposeLibBase/\r
+ ...\r
+\r
+ GeneralPurposeLibSerial/\r
+ ...\r
+\r
+ SpecificLibDxe/\r
+ SpecificLibDxe.c\r
+ SpecificLibDxe.inf\r
+ UnitTest/ # Host-Based Test for Specific Library Implementation\r
+ SpecificLibDxeHostUnitTest.c\r
+ SpecificLibDxeHostUnitTest.inf\r
+ Test/\r
+ <Package>HostTest.dsc # Host-Based Test Apps\r
+ UnitTest/\r
+ InterfaceX\r
+ InterfaceXHostUnitTest.inf # Host-Based App (should be in Test/<Package>HostTest.dsc)\r
+ InterfaceXPeiUnitTest.inf # PEIM Target-Based Test (if applicable)\r
+ InterfaceXDxeUnitTest.inf # DXE Target-Based Test (if applicable)\r
+ InterfaceXSmmUnitTest.inf # SMM Target-Based Test (if applicable)\r
+ InterfaceXShellUnitTest.inf # Shell App Target-Based Test (if applicable)\r
+ InterfaceXUnitTest.c # Test Logic\r
+\r
+ GeneralPurposeLib/ # Host-Based Test for any implementation of GeneralPurposeLib\r
+ GeneralPurposeLibTest.c\r
+ GeneralPurposeLibHostUnitTest.inf\r
+\r
+ <Package>Pkg.dsc # Standard Modules and any Target-Based Test Apps (including in Test/)\r
+\r
+```\r
+\r
+### Future Locations in Consideration\r
+\r
+We don't know if these types will exist or be applicable yet, but if you write a support library or module that matches the following, please make sure they live in the correct place.\r
+\r
+Code/Test | Location\r
+--------- | --------\r
+Host-Based Library Implementations | Host-Based Implementations of common libraries (eg. MemoryAllocationLibHost) should live in the same package that declares the library interface in its .DEC file in the `*Pkg/HostLibrary` directory. Should have 'Host' in the name.\r
+Host-Based Mocks and Stubs | Mock and Stub libraries should live in the `UefiTestFrameworkPkg/StubLibrary` with either 'Mock' or 'Stub' in the library name.\r
+\r
+### If still in doubt...\r
+\r
+Hop on GitHub and ask @corthon, @mdkinney, or @spbrogan. ;)\r
+\r
## Copyright\r
\r
Copyright (c) Microsoft Corporation.\r
SPDX-License-Identifier: BSD-2-Clause-Patent\r
-\r
projects / mirror_edk2.git / commitdiff