Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

QA_in_OpenCV

Alexander Alekhin edited this pageFeb 5, 2018 ·2 revisions

QA in OpenCV

C++ tests

You can start from the section 9 inOpenCV Coding Style Guide.

Same tests are used on every supported platform: Windows, Linux, MacOS and Android. Majority of testing is performed using C++ API, because it is the preffered language in the OpenCV project. These tests are implemented on top ofGoogle Test unit-testing framework.

There are two major types of C++ tests:accuracy/regression tests andperformance tests. Each module can have two test binaries:opencv_test_<MODULE_NAME> andopencv_perf_<MODULE_NAME>. These applications can be built for every supported platform (Win/Lin/Mac/Android).

Please note that you should setOPENCV_TEST_DATA_PATH environment variable (see section 9 inOpenCV Coding Style Guilde). On Android you should copy test data to the/sdcard/opencv_testdata directory:

git clone git://github.com/opencv/opencv_extra.git.adb push ./testdata /sdcard/opencv_testdata

Accuracy Tests

OpenCV library is actively developed, hence a set of regression tests is required. At the same time conformance between different platforms (both software and hardware) should be controlled, this is vital for keeping computer vision algorithms portable. For these two purposes OpenCV contains so-called accuracy tests. These unit-tests execute OpenCV functions with different parameters (input/output matrices sizes, number of channels, algorithm parameters and finally input data) and test it against some reference/desired output.

Every OpenCV module (core,imgproc, etc) has a set of accuracy tests, and their sources can be found in OpenCV repository inmodules/<MODULE_NAME>/test directories. For examplemodules/core/test andmodules/imgproc/test.

Performance Tests

Performance tests sources are located in themodules/<MODULE_NAME>/perf directories. For examplemodules/core/perf andmodules/imgproc/perf.

More technical information about performance tests can be found in the following documents:

Java Tests

  • Java testing on Android
  • Java testing on desktop:
    • Set environment variableOPENCV_TEST_DATA_PATH
    • Runpython <opencv>/modules/ts/misc/run.py . -a -t java from the build directory

BuildBot

OpenCV's continuous integration system is available here:http://pullrequest.opencv.org. There are also separate build-slaves fordocumentation, distribution package, test coverage calculation and some others. Additionally a small subset of builders is run on every commit to the OpenCV source code repository.

Documentation

Documentation update check list for public releases:

  • Check all images manually. Update images, that include OpenCV version, if it is needed by context;

  • Check all .rst files. Find docs with links to old versions of OpenCV: 2.4.3, 2.4.2, 2.4.1, 2.4.0, 2.3.1, 2.3.0, etc and update if needed;

    Search command for Unix/Linux systems:

    grep -R 2\\.[3-4]\\.[0-2]*

© Copyright 2019-2025, OpenCV team

Clone this wiki locally


[8]ページ先頭

©2009-2025 Movatter.jp