OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/scripts/requirements-build-test.txt

25 lines
430 B
Plaintext
Raw Normal View History

scripts/requirements: Split & document requirement.txt Split up requirements.txt into several files so that CI tools can utilize/reference the specific requirements-<FOO>.txt they may need while keep things in sync with the development. This is to reduce both time and amount of work CI actions due to python package install. Create the following groupings: 1. BASE - needed to build or create zephyr images 2. BUILD-TEST - need to run compile/build tests 3. DOC - need to build the docs 4. RUN-TEST - need for runtime testing 5. EXTRAS - optional or useful for development/developers workflow Also tried to add a comment about what or why a given package is being pulled in for. Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2020-02-08 04:58:00 +08:00
# BUILD-TEST: required to do build tests of zephyr
#
# things used by sanitycheck or other things like code coverage or python
# testing
# used by sanitycheck for ansi color
colorama
# python lex/yex used by sanitycheck
ply>=3.10
# optional, but used for validation of YAML
pykwalify
# used for code coverage
gcovr>=4.2
scripts: tests: sanitycheck: Add basic foundation for sanitycheck testsuite This commit adds basic testcases for sanitycheck tool using pytest. Coverage for the sanitycheck tool is obtained using coverage tool. Instructions are included in the README.md in scripts/tests/sanitycheck directory. Signed-off-by: Aastha Grover <aastha.grover@intel.com>
2020-03-20 06:27:27 +08:00
coverage
scripts/requirements: Split & document requirement.txt Split up requirements.txt into several files so that CI tools can utilize/reference the specific requirements-<FOO>.txt they may need while keep things in sync with the development. This is to reduce both time and amount of work CI actions due to python package install. Create the following groupings: 1. BASE - needed to build or create zephyr images 2. BUILD-TEST - need to run compile/build tests 3. DOC - need to build the docs 4. RUN-TEST - need for runtime testing 5. EXTRAS - optional or useful for development/developers workflow Also tried to add a comment about what or why a given package is being pulled in for. Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2020-02-08 04:58:00 +08:00
# used for west-command testing
pytest
scripts: runners: add type checking for west_commands Use mypy to type check the runners package. The test procedure is now annoying enough to replicate locally that I'm going to wrap it in a script. Do this for both UNIX and Windows environments by writing that script in Python. Keep the GitHub workflow up to date so we now get mypy results in CI. Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no>
2020-08-22 06:47:22 +08:00
mypy
tests: sanitycheck: Testcases for load_from_file and apply_filters test_testsuite_class.py: Added testcases for load_From_file and apply_filters functions of Class Testsuite. conftest.py: Modified class_testsuite fixture to create the outdir as temporary directory which gets deleted after execution of testcases. test_data/sanitycheck.csv: load_from_file function uses this customized file to load the failed or last run testcases. test_data/sanitycheck_keyerror.csv: file used by test_load_from_file function to raise the appropriate error if there is a keyerror. scripts/requirements-build-test.txt: added mock & csv python libraries Signed-off-by: Aastha Grover <aastha.grover@intel.com>
2020-06-02 07:08:20 +08:00
# used for mocking functions in pytest
requirements-build-test.txt: Updating mock module version Updating mock module version to >=4.0.1 as sanitycheck testsuite might fail in some systems due to old version. Signed-off-by: Aastha Grover <aastha.grover@intel.com>
2020-07-09 12:39:05 +08:00
mock>=4.0.1