diff --git a/doc/contribute/index.rst b/doc/contribute/index.rst index f27373301d9..b41fde1f520 100644 --- a/doc/contribute/index.rst +++ b/doc/contribute/index.rst @@ -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 diff --git a/doc/contribute/project_roles.rst b/doc/contribute/project_roles.rst index ae697437295..5cba6fc5586 100644 --- a/doc/contribute/project_roles.rst +++ b/doc/contribute/project_roles.rst @@ -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 diff --git a/doc/development_process/dev_env_and_tools.rst b/doc/development_process/dev_env_and_tools.rst index 08c993160ab..1b2cc06a082 100644 --- a/doc/development_process/dev_env_and_tools.rst +++ b/doc/development_process/dev_env_and_tools.rst @@ -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. diff --git a/doc/guides/coverage.rst b/doc/guides/coverage.rst index c54ef0be3c7..9c97dc994f9 100644 --- a/doc/guides/coverage.rst +++ b/doc/guides/coverage.rst @@ -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 ` can automatically generate a coverage report from the tests which were executed. diff --git a/doc/guides/modules.rst b/doc/guides/modules.rst index 3ff16566b5a..cac1aa307af 100644 --- a/doc/guides/modules.rst +++ b/doc/guides/modules.rst @@ -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 diff --git a/doc/guides/test/ztest.rst b/doc/guides/test/ztest.rst index 3544c33dd3c..4b917ad30ad 100644 --- a/doc/guides/test/ztest.rst +++ b/doc/guides/test/ztest.rst @@ -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