|author||Brendan Higgins <firstname.lastname@example.org>||2019-11-19 15:38:10 -0800|
|committer||Shuah Khan <email@example.com>||2019-12-09 11:21:22 -0700|
|parent||kunit: testing kunit: Bug fix in test_run_timeout function (diff)|
Documentation: kunit: fix typos and gramatical errors
Fix typos and gramatical errors in the Getting Started and Usage guide for KUnit. Reported-by: Randy Dunlap <firstname.lastname@example.org> Link: https://patchwork.kernel.org/patch/11156481/ Reported-by: Rinat Ibragimov <email@example.com> Link: https://github.com/google/kunit-docs/issues/1 Signed-off-by: Brendan Higgins <firstname.lastname@example.org> Reviewed-by: David Gow <email@example.com> Acked-by: Randy Dunlap <firstname.lastname@example.org> Signed-off-by: Shuah Khan <email@example.com>
Diffstat (limited to 'Documentation/dev-tools/kunit/usage.rst')
1 files changed, 12 insertions, 12 deletions
diff --git a/Documentation/dev-tools/kunit/usage.rst b/Documentation/dev-tools/kunit/usage.rst
index c6e69634e274..b9a065ab681e 100644
@@ -16,7 +16,7 @@ Organization of this document
This document is organized into two main sections: Testing and Isolating
-Behavior. The first covers what a unit test is and how to use KUnit to write
+Behavior. The first covers what unit tests are and how to use KUnit to write
them. The second covers how to use KUnit to isolate code and make it possible
to unit test code that was otherwise un-unit-testable.
@@ -174,13 +174,13 @@ Test Suites
Now obviously one unit test isn't very helpful; the power comes from having
-many test cases covering all of your behaviors. Consequently it is common to
-have many *similar* tests; in order to reduce duplication in these closely
-related tests most unit testing frameworks provide the concept of a *test
-suite*, in KUnit we call it a *test suite*; all it is is just a collection of
-test cases for a unit of code with a set up function that gets invoked before
-every test cases and then a tear down function that gets invoked after every
-test case completes.
+many test cases covering all of a unit's behaviors. Consequently it is common
+to have many *similar* tests; in order to reduce duplication in these closely
+related tests most unit testing frameworks - including KUnit - provide the
+concept of a *test suite*. A *test suite* is just a collection of test cases
+for a unit of code with a set up function that gets invoked before every test
+case and then a tear down function that gets invoked after every test case
@@ -211,7 +211,7 @@ KUnit test framework.
A test case will only be run if it is associated with a test suite.
-For a more information on these types of things see the :doc:`api/test`.
+For more information on these types of things see the :doc:`api/test`.
@@ -338,7 +338,7 @@ We can easily test this code by *faking out* the underlying EEPROM:
- ssize_t fake_eeprom_write(struct eeprom *this, size_t offset, const char *buffer, size_t count)
+ ssize_t fake_eeprom_write(struct eeprom *parent, size_t offset, const char *buffer, size_t count)
struct fake_eeprom *this = container_of(parent, struct fake_eeprom, parent);
@@ -454,7 +454,7 @@ KUnit on non-UML architectures
By default KUnit uses UML as a way to provide dependencies for code under test.
Under most circumstances KUnit's usage of UML should be treated as an
implementation detail of how KUnit works under the hood. Nevertheless, there
-are instances where being able to run architecture specific code, or test
+are instances where being able to run architecture specific code or test
against real hardware is desirable. For these reasons KUnit supports running on
@@ -557,7 +557,7 @@ run your tests on your hardware setup just by compiling for your architecture.
Always prefer tests that run on UML to tests that only run under a particular
architecture, and always prefer tests that run under QEMU or another easy
- (and monitarily free) to obtain software environment to a specific piece of
+ (and monetarily free) to obtain software environment to a specific piece of
Nevertheless, there are still valid reasons to write an architecture or hardware