tweak script to make it more accurate

* update list of "kunit devs", this makes the external contribution
count go down by 24+
* don't count merge commits as test patches
* don't count files like mm/slub.c as test files (this made the test
contributors shoot up to >200 since 5.13)
  * change it to look for files that contain "test" or "_kunit"
* also add a "-v" flag to dump the full list of tests and authors to
make debugging easier

Current output is:
Unique contributors:	26
Number of patches:	53
Number of total tests:	29
Number of test authors:	47

Change-Id: I1ec5abe14d650b2901cafe927c87e865b931882c
Signed-off-by: Daniel Latypov <>
1 file changed
tree: 79c716313bb34095d6882cf58d2da2c43e521c07
  1. .gitignore
  4. Makefile
  8. development/
  10. index.rst
  11. press.rst
  12. statics/
  13. third_party/
  14. usage/

KUnit Documentation

KUnit is a lightweight unit testing and mocking framework for the Linux kernel. These tests are able to be run locally on a developer’s workstation without a VM or special hardware.

KUnit is heavily inspired by JUnit, Python’s unittest.mock, and Googletest/Googlemock for C++. KUnit defines a way to mock out C style classes and functions and create expectations on methods called within the code under test.

This is a repository to host the source for the KUnit documentation.

NOTE: There is an important distinction between KUnit‘s documentation source and it’s documentation site. As a project meant primarily to serve the development of the Linux kernel, a significant portion of our code and documentation reside in the Linux kernel codebase. Consequently, the documentation that does not live in the Linux kernel follows many of the conventions of the Linux kernel. One of these conventions is that we use Sphinx for all of our documentation. Thus, because Sphinx requires documentation to be compiled from its source files, we must have a repository for all the Sphinx source files and a separate repository for all of the generated output files to actually host the site. This is the repository for the source.

Where is the code?

How to build documentation

Documentation can be built by running:

make html

How to update the documentation

Our documentation is hosted at The documentation may be updated by building the documentation as described above, and then:


You can copy the files over without committing and pushing the files with:

./ --no-commit