diff options
author | Laszlo Ersek <lersek@redhat.com> | 2014-08-12 07:29:17 +0000 |
---|---|---|
committer | jljusten <jljusten@6f19259b-4bc3-4df7-8a09-765794883524> | 2014-08-12 07:29:17 +0000 |
commit | 424d84556d4dfe3b05af00c06fd5d3480dccb111 (patch) | |
tree | 17de7ed9d7b789b4c641e6ecdcf2e350561ccb26 /AppPkg/ReadMe.txt | |
parent | cf556c6a587462cf916272597b34b9951279e7b6 (diff) | |
download | edk2-424d84556d4dfe3b05af00c06fd5d3480dccb111.zip edk2-424d84556d4dfe3b05af00c06fd5d3480dccb111.tar.gz edk2-424d84556d4dfe3b05af00c06fd5d3480dccb111.tar.bz2 |
AppPkg: introduce OrderedCollectionTest
In this patch a small application is added to AppPkg, with the following
two goals:
- demonstrate how to use OrderedCollectionLib,
- allow users to test and "fuzz" BaseOrderedCollectionRedBlackTreeLib in
particular, entering API "commands" interactively, or providing them
from a script file.
A shell script is included that generates such an API command script.
Speaking about BaseOrderedCollectionRedBlackTreeLib specifically,
OrderedCollectionTest validates the internal red-black properties of the
tree after each read-write operation by setting the
PcdValidateOrderedCollection feature flag to TRUE.
The OrderedCollectionTest application's debugging environment is strictly
specified in the DSC file, because OrderedCollectionTest is entirely
useless for unit testing without full ASSERT() enablement.
The OrderedCollectionTest application deliberately doesn't follow the edk2
coding style in the following:
- const vs. CONST,
- void vs. VOID,
- assert() vs. ASSERT(),
- calloc() and free() vs. AllocateZeroPool() and FreePool(),
- integer types.
This is because OrderedCollectionTest is a standard C application, not a
UEFI application per se. In particular it relies on stdio. INTN, EFIAPI
and CONST VOID are used only in two places, where we provide the
comparator callbacks to OrderedCollectionLib. Proper range checking is
ensured for integers.
The application takes command input from stdin or a file (if the user
requests it), sends command output to stdout or a file (if the user
requests it), prints debug output to the console (as other AppPkg
applications do when debugging is enabled for them), and prints
diagnostics to stderr (like well behaved standard C programs should).
Input/output selection is implemented manually because the old shell
doesn't support input redirection at all, and because the new shell's
input redirection does not co-operate with fgets() for the time being.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Laszlo Ersek <lersek@redhat.com>
Reviewed-by: Michael Kinney <michael.d.kinney@intel.com>
git-svn-id: https://svn.code.sf.net/p/edk2/code/trunk/edk2@15792 6f19259b-4bc3-4df7-8a09-765794883524
Diffstat (limited to 'AppPkg/ReadMe.txt')
-rw-r--r-- | AppPkg/ReadMe.txt | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/AppPkg/ReadMe.txt b/AppPkg/ReadMe.txt index 35e3b6a..3d41588 100644 --- a/AppPkg/ReadMe.txt +++ b/AppPkg/ReadMe.txt @@ -48,6 +48,12 @@ The EADK is comprised of three packages: See the PythonReadMe.txt file, in the Python directory,
for information on configuring and building Python.
+ OrderedCollectionTest A small Standard C Library application that
+ demonstrates the use of the OrderedCollectionLib library class
+ (provided by the BaseOrderedCollectionRedBlackTreeLib library
+ instance in this application), and allows the user to "fuzz" the
+ library with interactive or scripted API calls.
+
Sockets A collection of applications demonstrating use of the
EDK II Socket Libraries. These applications include:
|