Lines Matching +refs:run +refs:many +refs:tests

11 ``pw_unit_test`` is a portable library which can run on almost any system from
14 communicating its results through a common interface. Unit tests can be written
15 once and run under many different environments, empowering developers to write
18 ``pw_unit_test`` is still under development and lacks many features expected in
26 Writing unit tests
48 As the framework runs tests, it calls the event handler's callback functions to
63     [==========] Running all tests.
80     [==========] Done running all tests.
87 .. _running-tests:
89 Running tests
91 To run unit tests, link the tests into a single binary with the unit testing
114 If using C++17, filters can be set on the test framework to run only a subset of
115 the registered unit tests. This is useful when many tests are bundled into a
127 simple unit tests, set the ``pw_unit_test_MAIN`` build variable to a target
128 which configures the test framework as described in the :ref:`running-tests`
141  - ``simple_printing_event_handler```: When running tests, output test results
144    tests using the ``simple_printing_event_handler``.
145  - ``logging_event_handler``: When running tests, log test results as
147  - ``logging_main``: Implements a ``main()`` function that simply runs tests
157 * ``<target_name>.run``: If ``pw_unit_test_AUTOMATIC_RUNNER`` is set, this
167 * ``test_main``: Target label to add to the tests's dependencies to provide the
185 ``pw_test_group`` defines a collection of tests or other test groups. It creates
189 * ``<target_name>.run``: If ``pw_unit_test_AUTOMATIC_RUNNER`` is set, this
190   target runs all of the tests in the group and all of its group dependencies
192 * ``<target_name>.lib``: The sources of all of the tests in this group and its
194 * ``<target_name>.bundle``: All of the tests in the group and its dependencies
196 * ``<target_name>.bundle.run``: Automatic runner for the test bundle.
200 * ``tests``: List of the ``pw_test`` targets in the group.
212   pw_test_group("tests") {
213     tests = [
229 Pigweed facade test templates allow individual unit tests to build under the
231 This allows these tests to replace a facade's backend for the purpose of testing
235    Facade tests are costly because each facade test will trigger a re-build of
246 ``pw_unit_test`` provides an RPC service which runs unit tests on demand and
251 To set up RPC-based unit tests in your application, instantiate a
271 All tests flashed to an attached device can be run via python by calling