alex/esp-idf
alex/esp-idf
1
0
Fork 0
mirror of https://github.com/espressif/esp-idf.git synced 2024-10-05 20:47:46 -04:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity
89fb104747
esp-idf/tools/kconfig_new/test/confserver
History
Angus Gratton 89fb104747 confserver: Standardize and document the handling of hex values 
Previously, server always sent back "hex" types as JSON integers but would only accept setting them as a
JSON string of hex digits. This still works, but also possible to use JSON integers in both directions.

Add tests for both representations, add a note in the README about types.
2020-02-17 17:21:22 +11:00
..
Kconfig Docs: Omit kconfig configurations not available for the target 2020-01-30 10:30:06 +01:00
README.md Docs: Omit kconfig configurations not available for the target 2020-01-30 10:30:06 +01:00
sdkconfig Docs: Omit kconfig configurations not available for the target 2020-01-30 10:30:06 +01:00
test_confserver.py Docs: Omit kconfig configurations not available for the target 2020-01-30 10:30:06 +01:00
testcases_v1.txt Docs: Omit kconfig configurations not available for the target 2020-01-30 10:30:06 +01:00
testcases_v2.txt confserver: Standardize and document the handling of hex values 2020-02-17 17:21:22 +11:00

README.md

KConfig Tests

confserver.py tests

Install pexpect (pip install pexpect).

Then run the tests manually like this:

./test_confserver.py --logfile tests.log

If a weird error message comes up from the test, check the log file (tests.log) which has the full interaction session (input and output) from confserver.py - sometimes the test suite misinterprets some JSON-like content in a Python error message as JSON content.

Note: confserver.py prints its error messages on stderr, to avoid overlap with JSON content on stdout. However pexpect uses a pty (virtual terminal) which can't distinguish stderr and stdout.

Test cases apply to KConfig config schema. Cases are listed in testcases.txt and are each of this form:

* Set TEST_BOOL, showing child items
> { "TEST_BOOL" : true }
< { "values" : { "TEST_BOOL" : true, "TEST_CHILD_STR" : "OHAI!", "TEST_CHILD_BOOL" : true }, "ranges": {"TEST_CONDITIONAL_RANGES": [0, 100]}, "visible": {"TEST_CHILD_BOOL" : true, "TEST_CHILD_STR" : true} }
  • First line (*) is description
  • Second line (>) is changes to send
  • Third line (<) is response to expect back
  • (Blank line between cases)

Test cases are run in sequence, so any test case depends on the state changes caused by all items above it.