Lines Matching +full:api +full:- +full:coverage

20 been completed. This allows for testing that high-level code can
21 handle these situations correctly. Test coverage can therefore
27 The diagram below shows application code / high-level tests at the top.
39 Separately we can test the STM32 and NXP I2C drivers on real hardware using API
49 Controller) on native_sim using emulators for all non-chip drivers.
56 * Ensure 100% test coverage for drivers (green)
63   native_sim. We can develop on a host, use source-level debugging, etc.
79 .. code-block:: C
87 The ``EMUL_DT_DEFINE()`` function accepts two API types:
89   #. ``bus_api`` - This points to the API for the upstream bus that the emulator
92   #. ``_backend_api`` - This points to the device-class specific backend API for
97 device-class.
112 out of band.  Each device class defines it's own API functions.  The backend API
113 functions focus on high-level behavior and do not provide hooks for specific
116 In the case of the BC1.2 charging detector the backend API provides functions
123   #. Test registers BC1.2 detection callback using the Zephyr BC1.2 driver API.
148 ----------------------
153 .. code-block:: devicetree
157      compatible = "zephyr,i2c-emul-controller";
158      clock-frequency = <I2C_BITRATE_STANDARD>;
159      #address-cells = <1>;
160      #size-cells = <0>;
161      #forward-cells = <1>;
172    The ``#forward-cells`` attribute should always be 1. Each entry in the
186    .. zephyr-app-commands::
187       :zephyr-app: tests/drivers/sensor/bmi160
194    .. zephyr-app-commands::
195       :zephyr-app: tests/drivers/eeprom/api
198       :gen-args: -DDTC_OVERLAY_FILE=at2x_emul.overlay -DEXTRA_CONF_FILE=at2x_emul.conf
200 API Reference