| /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 will be a separate static libcurl built that will be
16 used exclusively for linking unit test programs. Just build everything as
17 normal, and then you can run the unit test cases as well.
[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/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/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/config.h
22 # which can lead to some tests being skipped, and can cause the number of
[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/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/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/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`
29 * :ref:`module-pw_third_party_re2-using_upstream`
31 .. tab-set::
[all …]
|
| /external/rust/crates/libz-sys/src/zlib/contrib/dotzlib/ |
| D | readme.txt | 8 --------------------
10 LICENSE_1_0.txt - License file.
11 readme.txt - This file.
12 DotZLib.chm - Class library documentation
13 DotZLib.build - NAnt build file
14 DotZLib.sln - Microsoft Visual Studio 2003 solution file
16 DotZLib\*.cs - Source files for the class library
18 Unit tests:
19 -----------
20 The file DotZLib/UnitTests.cs contains unit tests for use with NUnit 2.1 or higher.
[all …]
|
| /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/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/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 …]
|
| /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/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/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/python/python-api-core/ |
| D | noxfile.py | 7 # http://www.apache.org/licenses/LICENSE-2.0
21 import nox # pytype: disable=import-error
25 BLACK_PATHS = ["docs", "google", "tests", "noxfile.py", "setup.py"]
27 BLACK_EXCLUDES = ["--exclude", "^/google/api_core/operations_v1/__init__.py"]
32 # 'docfx' is excluded since it only needs to run in 'docs-presubmit'
34 "unit",
64 session.install("flake8", "flake8-import-order", BLACK_VERSION)
67 "black", "--check", *BLACK_EXCLUDES, *BLACK_PATHS,
69 session.run("flake8", "google", "tests")
83 """Default unit test session.
[all …]
|
| /external/skia/site/docs/dev/testing/ |
| D | testing.md | 1 ---
4 ---
9 <!--?prettify lang=sh?-->
11 python3 tools/git-sync-deps
13 ninja -C out/Debug dm
14 out/Debug/dm -v -w dm_output
18 multithreaded, but some of the work, particularly GPU-backed work, is still
19 forced to run on a single thread. You can use `--threads N` to limit DM to N
30 492 srcs * 3 sinks + 382 tests == 1858 tasks
32 ( 25MB 1857) 1.36ms 8888 image mandrill_132x132_12x12.astc-5-subsets
[all …]
|
| /external/kotlinx.coroutines/reactive/kotlinx-coroutines-rx3/test/ |
| D | SchedulerTest.kt | 2 …* Copyright 2016-2018 JetBrains s.r.o. Use of this source code is governed by the Apache 2.0 licen… in <lambda>()
24 … ignoreLostThreads("RxCachedThreadScheduler-", "RxCachedWorkerPoolEvictor-", "RxSchedulerPurge-") in <lambda>()
28 fun testIoScheduler(): Unit = runTest { in <lambda>()
43 …/** Tests [toString] implementations of [CoroutineDispatcher.asScheduler] and its [Scheduler.Worke… in <lambda>()
57 private fun runSchedulerTest(nThreads: Int = 1, action: (Scheduler) -> Unit) { in <lambda>()
58 val future = CompletableFuture<Unit>() in <lambda>()
60 newFixedThreadPoolContext(nThreads, "test").use { dispatcher -> in <lambda>()
71 future.complete(Unit) in <lambda>()
72 future.getNow(Unit) // rethrow any encountered errors in <lambda>()
75 …reSeparateThread(schedule: (Runnable, Long, TimeUnit) -> Unit, scheduleNoDelay: (Runnable) -> Unit… in <lambda>()
[all …]
|
| /external/kotlinx.coroutines/reactive/kotlinx-coroutines-rx2/test/ |
| D | SchedulerTest.kt | 2 …* Copyright 2016-2018 JetBrains s.r.o. Use of this source code is governed by the Apache 2.0 licen… in <lambda>()
24 … ignoreLostThreads("RxCachedThreadScheduler-", "RxCachedWorkerPoolEvictor-", "RxSchedulerPurge-") in <lambda>()
28 fun testIoScheduler(): Unit = runTest { in <lambda>()
43 …/** Tests [toString] implementations of [CoroutineDispatcher.asScheduler] and its [Scheduler.Worke… in <lambda>()
57 private fun runSchedulerTest(nThreads: Int = 1, action: (Scheduler) -> Unit) { in <lambda>()
58 val future = CompletableFuture<Unit>() in <lambda>()
60 newFixedThreadPoolContext(nThreads, "test").use { dispatcher -> in <lambda>()
71 future.complete(Unit) in <lambda>()
72 future.getNow(Unit) // rethrow any encountered errors in <lambda>()
75 …reSeparateThread(schedule: (Runnable, Long, TimeUnit) -> Unit, scheduleNoDelay: (Runnable) -> Unit… in <lambda>()
[all …]
|
| /external/pigweed/pw_unit_test/ |
| D | docs.rst | 1 .. _module-pw_unit_test:
6 .. pigweed-module::
9 .. tab-set::
11 .. tab-item:: mylib_test.cpp
13 .. code-block:: c++
29 .. tab-item:: BUILD.bazel
31 .. code-block:: python
52 .. tab-item:: mylib.cc
54 .. code-block:: c++
69 .. tab-item:: mylib.h
[all …]
|
| /external/cronet/components/cronet/android/ |
| D | test_instructions.md | 10 ## Running tests locally
13 device](/docs/android_build_instructions.md#Plug-in-your-Android-device)
16 Alternatively, you can pass the --x86 flag to `gn` to test on a local emulator
17 -- make sure you substitute `out/Debug` for `out/Debug-x86` in the instructions
20 ### Running Cronet Java unit tests
22 To run Java unit tests that actuate the Cronet API:
26 $ ./components/cronet/tools/cr_cronet.py build-test
29 To run particular tests specify the test class and method name to the build-test
33 $ ./components/cronet/tools/cr_cronet.py build-test -f QuicTest#testQuicLoadUrl
38 To run C++ and Java unit tests of net/ functionality:
[all …]
|
| /external/mbedtls/docs/architecture/testing/ |
| D | test-framework.md | 7 ## Unit tests
9 See <https://mbed-tls.readthedocs.io/en/latest/kb/development/test_suites>
11 ### Unit test descriptions
13 … succinctly describes for a human audience what the test does. The first non-comment line of each …
15 * Test descriptions may not contain semicolons, line breaks and other control characters, or non-AS…
16 …at process test descriptions (`generate_test_code.py`, [outcome file](#outcome-file) tools) simple.
18 …a failure log to the test data. Avoid confusion between cases in the [outcome file](#outcome-file).
20 … what our various tools assume (leaving room for 14 more characters on an 80-column line). Longer …
25 `tests/scripts/check_test_cases.py` enforces some rules and warns if some guidelines are violated.
27 ## TLS tests
[all …]
|
| /external/openthread/third_party/mbedtls/repo/docs/architecture/testing/ |
| D | test-framework.md | 7 ## Unit tests
9 See <https://mbed-tls.readthedocs.io/en/latest/kb/development/test_suites>
11 ### Unit test descriptions
13 … succinctly describes for a human audience what the test does. The first non-comment line of each …
15 * Test descriptions may not contain semicolons, line breaks and other control characters, or non-AS…
16 …at process test descriptions (`generate_test_code.py`, [outcome file](#outcome-file) tools) simple.
18 …a failure log to the test data. Avoid confusion between cases in the [outcome file](#outcome-file).
20 … what our various tools assume (leaving room for 14 more characters on an 80-column line). Longer …
25 `tests/scripts/check_test_cases.py` enforces some rules and warns if some guidelines are violated.
27 ## TLS tests
[all …]
|