| /external/coreboot/Documentation/technotes/ |
| D | 2021-05-code-coverage.md | 1 # Unit Test Code Coverage
3 Code coverage for the coreboot unit tests allows us to see what lines of
4 code in the coreboot library are covered by unit tests, and allows a test
10 Enable code coverage in your unit test build by setting the environment
12 `make` command, e.g. `COV=1 make unit-tests`.
14 The build output directory is either `build/tests` or `build/coverage`,
17 All of the unit test targets are available with and without `COV=1`
18 * `clean-unit-tests`
19 * `build-unit-tests`
20 * `run-unit-tests`
[all …]
|
| D | 2020-03-unit-testing-coreboot.md | 1 # Unit testing coreboot
5 unit testing is and what is not. This definition will be a basis for the whole
8 Next, Rationale, explains why to use unit testing and how coreboot specifically
11 This is followed by evaluation of different available free C unit test
16 Fourth part is a summary of evaluation, with proposal of unit test framework
20 codebase in general should be organized, in order to support unit testing. This
24 A unit test is supposed to test a single unit of code in isolation. In C
25 language (in contrary to OOP) unit usually means a function. One may also
26 consider unit under test to be a single compilation unit which exposes some
31 dependencies (executables) required beside unit under test and test harness in
[all …]
|
| /external/coreboot/tests/ |
| D | Makefile.mk | 1 # SPDX-License-Identifier: GPL-2.0-only
8 testobj := $(obj)/tests
13 include $(top)/tests/Makefile.common
18 TEST_CFLAGS += -g -Og
23 TEST_CFLAGS += --coverage
24 TEST_LDFLAGS += --coverage
31 subdirs := tests/arch tests/acpi tests/commonlib tests/console tests/cpu
32 subdirs += tests/device tests/drivers tests/ec tests/lib
33 subdirs += tests/mainboard tests/northbridge tests/security tests/soc
34 subdirs += tests/southbridge tests/superio tests/vendorcode
[all …]
|
| /external/curl/tests/unit/ |
| D | README.md | 1 <!--
4 SPDX-License-Identifier: curl
5 -->
7 # Unit tests
9 The goal is to add tests for *all* functions in libcurl. If functions are too
12 ## Build Unit Tests
14 `./configure --enable-debug` is required for the unit tests to build. To
15 enable unit tests, there is a separate static libcurl built that is used
16 exclusively for linking unit test programs. Just build everything as normal,
17 and then you can run the unit test cases as well.
[all …]
|
| /external/coreboot/payloads/libpayload/tests/ |
| D | Makefile.mk | 1 # SPDX-License-Identifier: GPL-2.0-only
3 testsrc := $(top)/tests
10 testobj := $(obj)/tests
12 coverage-dir := $(testobj)/coverage_reports
20 TEST_DEFAULT_CONFIG := $(top)/configs/config.unit-tests
22 TEST_KCONFIG_AUTOHEADER := $(testobj)/libpayload-config.src.h
33 TEST_CFLAGS := -include include/kconfig.h
34 TEST_CFLAGS += -include $(coreboottop)/src/commonlib/bsd/include/commonlib/bsd/compiler.h
35 TEST_CFLAGS += -Iinclude -Iinclude/mock
36 TEST_CFLAGS += -I$(coreboottop)/src/commonlib/bsd/include
[all …]
|
| /external/flashrom/doc/contrib_howtos/ |
| D | how_to_add_unit_test.rst | 2 How to add a unit test
5 Unit tests help to maintain higher bar for code quality. A new unit test which adds coverage to the…
6 no matter how small or large it is! Unit test is a valuable contribution, moreover it makes a good …
9 For more details on how to run unit tests and measure coverage, check the dev guide: :ref:`unit tes…
11 To see the examples of existing unit tests, check the ``/tests`` directory in the source tree. If i…
12 at git history for examples of previous commits that add new tests.
14 When is a good time to add a unit test? Any time is a good time. Test can go in its own separate pa…
17 Unit tests are using `cmocka <https://cmocka.org/>`_ as a mocking framework, but we also have flash…
23 Unit tests mock all interactions with hardware, interactions with filesystem, syscalls, 3rd party l…
24 (e.g. libusb, libpci) etc. You can think of a flashrom unit test as a mini-emulator. The goal is to…
[all …]
|
| /external/rappor/ |
| D | test.sh | 9 # http://www.apache.org/licenses/LICENSE-2.0
23 # $ ./test.sh py-unit # run Python unit tests
24 # $ ./test.sh all # all tests
26 # If no function is provided all of the unit tests will be run.
28 set -o nounset
29 set -o pipefail
30 set -o errexit
39 # Fully Automated Tests
42 # Run all Python unit tests.
46 # $ ./test.sh py-unit tests/fastrand_test.py
[all …]
|
| /external/crosvm/docs/book/src/testing/ |
| D | index.md | 3 Crosvm runs on a variety of platforms with a significant amount of platform-specific code. Testing
6 ## Types of tests
8 ### Unit Tests
10 Unit tests are your standard rust tests embedded with the rest of the code in `src/` and wrapped in
13 Unit tests **cannot make any guarantees on the runtime environment**. Avoid doing the following in
14 unit tests:
16 - Avoid kernel features such as io_uring or userfaultfd, which may not be available on all kernels.
17 - Avoid functionality that requires privileges (e.g. CAP_NET_ADMIN)
18 - Avoid spawning threads or processes
19 - Avoid accessing kernel devices
[all …]
|
| /external/openthread/tests/unit/ |
| D | README.md | 1 # OpenThread Unit Tests
3 … describes how to build and run OpenThread unit tests. It will be helpful for developers to debug …
7 …unit tests cannot be built solely without building the whole project. So first build OpenThread on…
11 $ script/cmake-build simulation
14 ## List all tests
16 To see what tests are available in OpenThread:
20 $ ctest -N
23 ## Run the Unit Tests
25 To run all the unit tests:
32 To run a specific unit test, for example, `ot-test-spinel`:
[all …]
|
| /external/cronet/tot/third_party/apache-portable-runtime/src/test/ |
| D | README | 1 Writing APR tests
3 All APR tests should be executable in 2 ways, as an individual program, or
6 array of functions called tests. The testall program loops through this
13 --------------
16 * then be used to actually run the tests. Essentially, all Suites are a
17 * collection of tests. The driver will take each Suite, and put it in a
30 * function, although no tests currently do that.
52 ------------------------
62 Running individual tests
63 ------------------------
[all …]
|
| /external/cronet/stable/third_party/apache-portable-runtime/src/test/ |
| D | README | 1 Writing APR tests
3 All APR tests should be executable in 2 ways, as an individual program, or
6 array of functions called tests. The testall program loops through this
13 --------------
16 * then be used to actually run the tests. Essentially, all Suites are a
17 * collection of tests. The driver will take each Suite, and put it in a
30 * function, although no tests currently do that.
52 ------------------------
62 Running individual tests
63 ------------------------
[all …]
|
| /external/mbedtls/tests/scripts/ |
| D | basic-build-test.sh | 3 # basic-build-test.sh
6 # SPDX-License-Identifier: Apache-2.0 OR GPL-2.0-or-later
13 # The tests include:
14 # * Unit tests - executed using tests/scripts/run-test-suite.pl
15 # * Self-tests - executed using the test suites above
16 # * System tests - executed using tests/ssl-opt.sh
17 # * Interoperability tests - executed using tests/compat.sh
19 # The tests focus on functionality and do not consider performance.
21 # Note the tests self-adapt due to configurations in include/mbedtls/mbedtls_config.h
22 # which can lead to some tests being skipped, and can cause the number of
[all …]
|
| /external/openthread/third_party/mbedtls/repo/tests/scripts/ |
| D | basic-build-test.sh | 3 # basic-build-test.sh
6 # SPDX-License-Identifier: Apache-2.0 OR GPL-2.0-or-later
13 # The tests include:
14 # * Unit tests - executed using tests/scripts/run-test-suite.pl
15 # * Self-tests - executed using the test suites above
16 # * System tests - executed using tests/ssl-opt.sh
17 # * Interoperability tests - executed using tests/compat.sh
19 # The tests focus on functionality and do not consider performance.
21 # Note the tests self-adapt due to configurations in include/mbedtls/mbedtls_config.h
22 # which can lead to some tests being skipped, and can cause the number of
[all …]
|
| /external/coreboot/Documentation/tutorial/ |
| D | part3.md | 1 # Writing unit tests for coreboot
4 General thoughts about unit testing coreboot can be found in
5 [Unit-testing coreboot](../technotes/2020-03-unit-testing-coreboot.md).
6 Additionally, [code coverage](../technotes/2021-05-code-coverage.md)
7 support is available for unit tests.
10 writing unit tests for coreboot modules.
12 As an example of unit-under-test, `src/device/i2c.c` (referred hereafter
13 as UUT "Unit Under Test") will be used. This is simple module, thus it
17 understanding of what the unit-under-test is doing is crucial for
18 writing unit tests.
[all …]
|
| /external/aws-sdk-java-v2/docs/ |
| D | GettingStarted.md | 6 * The majority of the service client code is auto-generated using the [code
10 If you use IntelliJ IDEA, the following config files will be used by default for your project-level…
12 - [Copyright](https://raw.githubusercontent.com/aws/aws-sdk-java-v2/master/.idea/copyright/AWS_Java…
16 - [Code style](https://raw.githubusercontent.com/aws/aws-sdk-java-v2/master/.idea/codeStyles/Projec…
20 - [Inspections](https://raw.githubusercontent.com/aws/aws-sdk-java-v2/master/.idea/inspectionProfil…
26 [Checkstyle config](https://raw.githubusercontent.com/aws/aws-sdk-java-v2/master/build-tools/src/ma…
47 $ mvn install -Dfindbugs.skip=true -Dcheckstyle.skip=true
51 #### Unit Tests
52 As described in the project structure, tests are split between unit and
53 integration tests. During the normal `test` lifecycle phase, only the unit
[all …]
|
| /external/libsrtp2/test/ |
| D | cutest.h | 2 * CUTest -- C/C++ Unit Test facility
5 * Copyright (c) 2013-2017 Martin Mitas
40 /* Macro to specify list of unit tests in the suite.
41 * The unit test implementation MUST provide list of unit tests it implements
60 /* Macros for testing whether an unit test succeeds or fails. These macros
61 * can be used arbitrarily in functions implementing the unit tests.
67 * (It expects printf-like format string and its parameters). The macros
68 * return non-zero (condition passes) or 0 (condition fails).
75 * TEST_CHECK(ptr->member1 < 100);
76 * TEST_CHECK(ptr->member2 > 200);
[all …]
|
| /external/pigweed/pw_fuzzer/guides/ |
| D | fuzztest.rst | 1 .. _module-pw_fuzzer-guides-using_fuzztest:
6 .. pigweed-module-subpage::
13 .. _module-pw_fuzzer-guides-using_fuzztest-toolchain:
15 ----------------------------------------
17 ----------------------------------------
26 * :ref:`module-pw_third_party_abseil_cpp-using_upstream`
27 * :ref:`module-pw_third_party_fuzztest-using_upstream`
28 * :ref:`module-pw_third_party_googletest-using_upstream`
30 .. tab-set::
32 .. tab-item:: GN
[all …]
|
| /external/compiler-rt/test/msan/Unit/ |
| D | lit.site.cfg.in | 3 # Load common config for all compiler-rt unit tests.
4 lit_config.load_config(config, "@COMPILER_RT_BINARY_DIR@/unittests/lit.common.unit.configured")
7 config.name = 'MemorySanitizer-Unit'
9 # Setup test source and exec root. For unit tests, we define
10 # it as build directory with MSan unit tests.
11 # FIXME: Don't use hardcoded path to MSan unit tests.
12 config.test_exec_root = "@COMPILER_RT_BINARY_DIR@/lib/msan/tests"
|
| /external/skia/modules/canvaskit/ |
| D | README.md | 3 Node v14 or later is required to run tests. We use npm (the Node Package Manager) to install
12 script in `//bin/activate-emsdk` (or `//tools/git-sync-deps` which also calls activate-emsdk).
25 can fail with errors about SSL certificates. <https://github.com/emscripten-core/emsdk/pull/273>
27 See also <https://github.com/emscripten-core/emscripten/issues/9036#issuecomment-532092743>
38 make local-example
46 For example, building a stripped-down version of CanvasKit with no text support or
51 Such a stripped-down version is about half the size of the default release build.
60 # Unit tests, performance tests, and coverage.
62 To run unit tests and compute test coverage on a debug gpu build
66 make test-continuous
[all …]
|
| /external/shflags/doc/ |
| D | RELEASE_NOTES-1.2.2.md | 14 Please see the `CHANGES-1.2.md` file for a complete list of changes.
18 Continuous integration testing setup with [Travis CI][travis-ci]. This helps
19 keep the code in a working state by executing the unit tests on every submit.
21 [travis-ci]: https://travis-ci.org/kward/shflags
35 ### The unit tests
38 environments are created equal. As such, not all of the unit tests will succeed
39 on every platform. The unit tests are therefore designed to fail, indicating to
46 version, some unit tests will be skipped (i.e. ASSERTS will not be thrown) when
49 of skipped tests will be kept for later reference.
56 --------------------------------------- | --- | ---
[all …]
|
| /external/chromiumos-config/proto/chromiumos/config/api/test/plan/v1/ |
| D | plan.proto | 2 // Use of this source code is governed by a BSD-style license that can be
20 // A Plan fully specifies a Test Platform end-user's coverage needs.
23 // coverage rules with tests that exercise those components. Plans MUST be used
34 // Each test plan unit specifies a particular set of tests to be run to meet
36 repeated Unit units = 2;
39 // Defines the device rule that must be met in for a given set of tests.
54 // E.g. kernel:5.4_soc:geminilake_wifi:intel-5600
66 // Specifies a particular set of tests to be run for a given set of coverage
68 message Unit { message
69 // A globally unique test plan unit name.
[all …]
|
| /external/compiler-rt/test/asan/ |
| D | CMakeLists.txt | 6 # TODO(wwchrome): Re-enable Win64 asan tests when ready.
7 # Disable tests for asan Win64 temporarily.
40 set(ASAN_TEST_TARGET_ARCH ${arch}-android)
44 string(TOLOWER "-${arch}-${OS_NAME}" ASAN_TEST_CONFIG_SUFFIX)
47 # This is only true if we are cross-compiling.
48 # Build all tests with host compiler and use host tools.
69 string(TOLOWER "-${arch}-${OS_NAME}-dynamic" ASAN_TEST_CONFIG_SUFFIX)
80 # Add unit tests.
84 ${CMAKE_CURRENT_SOURCE_DIR}/Unit/lit.site.cfg.in
85 ${CMAKE_CURRENT_BINARY_DIR}/Unit/lit.site.cfg)
[all …]
|
| /external/compiler-rt/test/tsan/Unit/ |
| D | lit.site.cfg.in | 3 # Load common config for all compiler-rt unit tests.
4 lit_config.load_config(config, "@COMPILER_RT_BINARY_DIR@/unittests/lit.common.unit.configured")
7 config.name = 'ThreadSanitizer-Unit'
9 # Setup test source and exec root. For unit tests, we define
10 # it as build directory with ASan unit tests.
11 # FIXME: De-hardcode this path.
12 config.test_exec_root = "@COMPILER_RT_BINARY_DIR@/lib/tsan/tests"
|
| /external/pigweed/pw_unit_test/py/pw_unit_test/ |
| D | test_runner.py | 7 # https://www.apache.org/licenses/LICENSE-2.0
14 """Runs Pigweed unit tests built using GN."""
45 def _strip_ansi(bytes_with_sequences: bytes) -> bytes:
50 def register_arguments(parser: argparse.ArgumentParser) -> None:
51 """Registers command-line arguments."""
54 '--root',
60 '-r',
61 '--runner',
67 '-m', '--timeout', type=float, help='Timeout for test runner in seconds'
70 '-e',
[all …]
|
| /external/google-auth-library-java/oauth2_http/javatests/com/google/auth/oauth2/ |
| D | AwsRequestSignerTest.java | 50 * Tests for {@link AwsRequestSigner}.
53 * https://docs.aws.amazon.com/general/latest/gr/sigv4-signed-request-examples.html
73 …oto/botocore/blob/879f8440a4e9ace5d3cf145ce8b3d5e5ffb892ef/tests/unit/auth/aws4_testsuite/get-vani…
74 …oto/botocore/blob/879f8440a4e9ace5d3cf145ce8b3d5e5ffb892ef/tests/unit/auth/aws4_testsuite/get-vani…
83 AwsRequestSigner.newBuilder(BOTOCORE_CREDENTIALS, "GET", url, "us-east-1") in sign_getHost()
91 "AWS4-HMAC-SHA256 Credential=AKIDEXAMPLE/20110909/us-east-1/host/" in sign_getHost()
100 assertEquals("us-east-1", signature.getRegion()); in sign_getHost()
104 …otocore/blob/879f8440a4e9ace5d3cf145ce8b3d5e5ffb892ef/tests/unit/auth/aws4_testsuite/get-relative-…
105 …otocore/blob/879f8440a4e9ace5d3cf145ce8b3d5e5ffb892ef/tests/unit/auth/aws4_testsuite/get-relative-…
114 AwsRequestSigner.newBuilder(BOTOCORE_CREDENTIALS, "GET", url, "us-east-1") in sign_getHostRelativePath()
[all …]
|