|author||Daniel Latypov <firstname.lastname@example.org>||Thu Apr 08 16:08:58 2021 -0700|
|committer||Daniel Latypov <email@example.com>||Thu Aug 05 16:39:48 2021 -0700|
mocking.rst: add discussion on how to get state in funcs for mocks/fakes This goes over using named resources and container_of(), as these are probably the two best ways we can demonstrate for stashing away some state. Signed-off-by: Daniel Latypov <firstname.lastname@example.org> Change-Id: I7804b75dd986a4df0cde4d8fea6b4b276029a039
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 https://github.com/google/kunit-docs. 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: