summaryrefslogtreecommitdiff
path: root/board/host/battery.c
diff options
context:
space:
mode:
authorCraig Hesling <hesling@chromium.org>2019-07-01 18:10:37 -0700
committerCommit Bot <commit-bot@chromium.org>2019-07-20 04:24:56 +0000
commit053491b560d2c4e374bb739373d8ae25c41f6315 (patch)
tree91b2330af33a7fcd43905ee0ecde0947d0877ecb /board/host/battery.c
parent7d29ac01ea9c3a6ac3aba2dcace88ca43e2d8201 (diff)
downloadchrome-ec-053491b560d2c4e374bb739373d8ae25c41f6315.tar.gz
Improve unit test and fuzzer documentation story
* Update **test** directory description to README.md. * Add ** fuzz** directory description to README.md. * Add unit test and fuzzer make targets to `make help` * Change showboards to print-boards to be more consistent * Change showboards to use auto pretty print * Add print-tests, print-host-tests, and print-host-fuzzers This is necessary to remove the ambiguity about what a special name is for a given unit test. Documentation Story: The idea is to give a brief overview of what the test and fuzz directories are in README.md. README.md also mentions you should see `make help` for more detail. Running `make help` shows you more general test/fuzz commands, including the print-* commands. Running the print-* commands show you exact target names for all possible unit/fuzz test (both the build-only and run target names). BRANCH=none BUG=none TEST=make help TEST=make print-tests TEST=make print-host-tests TEST=make print-host-fuzzers TEST=make print-host-fuzzers | cat TEST=make print-boards TEST=make print-boards | cat TEST=make buildall -j Change-Id: I34b68196ac635ba71a1d45ceb5d35a3b36fd129f Signed-off-by: Craig Hesling <hesling@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/1684714 Reviewed-by: Aseda Aboagye <aaboagye@chromium.org> Reviewed-by: Daisuke Nojiri <dnojiri@chromium.org>
Diffstat (limited to 'board/host/battery.c')
0 files changed, 0 insertions, 0 deletions