|author||David Gow <firstname.lastname@example.org>||Wed Jan 29 15:57:37 2020 -0800|
|committer||David Gow <email@example.com>||Thu Jan 30 14:53:00 2020 -0800|
Update website now that KUnit is upstream in 5.5 This fixes a few parts of the website which claim that KUnit is not upstream, and instead directs people to the upstream kernel (noting that 5.5 or later is required). The upstream documentation is now retrieved from torvalds/linux/master. It also fixes a couple of links in the usage/getting_kunit page to the documentation, which were broken. Change-Id: Ifd6b53498cfaa9433232b0beba34ee6dca646d48 Signed-off-by: David Gow <firstname.lastname@example.org>
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.
Documentation can be built by running:
Our documentation is hosted at http://github.com/google/kunit-docs. The documentation may be updated by building the documentation as described above, and then:
git clone http://github.com/google/kunit-docs.git cd kunit-docs/ git ls-files -z | xargs -0 rm -f cp -r ../kunit-website/_build/html/. ./ git add -A git commit git push -u origin