michaelh/zephyr
1
0
Fork 0
Code Releases Activity

doc: rename sanitycheck -> twister

Browse source 
Replace leftover sanitycheck mentions.

Signed-off-by: Anas Nashif <anas.nashif@intel.com>
This commit is contained in:
Anas Nashif 2020-12-11 17:57:30 -05:00
commit 7883eedfde
6 changed files with 9 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

2
doc/contribute/index.rst
View file

@ -221,7 +221,7 @@ every Pull Request (PR) in order to verify several aspects of the PR:
* Git commit formatting
* Coding Style
* Sanity Check builds for multiple architectures and boards
* Twister builds for multiple architectures and boards
* Documentation build to verify any doc changes
CI is run on the ``shippable`` cloud service and it uses the same tools

2
doc/contribute/project_roles.rst
View file

@ -228,7 +228,7 @@ Merge Criteria
* License
* Checkpatch (Coding Style)
* Pylint
* Sanitycheck + Other Unit tests
* Integration Tests (Via twister) on emulation/simulation platforms
* Simulated Bluetooth Tests
* Planned

4
doc/development_process/dev_env_and_tools.rst
View file

@ -198,9 +198,9 @@ Closing Stale Issues and Pull Requests
Continuous Integration
***********************
All changes submitted to GitHub are subject to sanity tests that are run on
All changes submitted to GitHub are subject to tests that are run on
emulated platforms and architectures to identify breakage and regressions that
can be immediately identified. Sanity testing additionally performs build tests
can be immediately identified. Testing using Twister additionally performs build tests
of all boards and platforms. Documentation changes are also verified
through review and build testing to verify doc generation will be successful.

4
doc/guides/coverage.rst
View file

@ -129,8 +129,8 @@ You may postprocess these with your preferred tools. For example:
Alternatively, you can use gcovr (at least version 4.2).
Sanitycheck coverage reports
****************************
Coverage reports using Twister
******************************
Zephyr's :ref:`twister script <twister_script>` can automatically
generate a coverage report from the tests which were executed.

4
doc/guides/modules.rst
View file

@ -536,8 +536,8 @@ requires the following folder structure:
Sanitycheck
===========
Twister (Test Runner)
=====================
To execute both tests and samples available in modules, the Zephyr test runner
(twister) should be pointed to the directories containing those samples and

2
doc/guides/test/ztest.rst
View file

@ -99,7 +99,7 @@ feature. The ``twister`` script can parse the testcases in all
test projects or a subset of them, and can generate reports on a granular
level, i.e. if cases have passed or failed or if they were blocked or skipped.
Sanitycheck parses the source files looking for test case names, so you
Twister parses the source files looking for test case names, so you
can list all kernel test cases, for example, by entering::
twister --list-tests -T tests/kernel