diff options
| author | Simon Glass <sjg@chromium.org> | 2021-03-07 17:35:17 -0700 |
|---|---|---|
| committer | Tom Rini <trini@konsulko.com> | 2021-03-12 09:57:31 -0500 |
| commit | fc3283314539d6c3fb577359f6cb364c19c13726 (patch) | |
| tree | 8b8b53585fd9bc655f32eba141f3c2d25d21d882 /doc/develop/py_testing.rst | |
| parent | e1b12e39452fba018e39c7d9005870ab80450b8c (diff) | |
doc: Explain briefly how to write new tests
Add a second on writing tests, covering when to use Python and C, where
to put the tests, etc. Add a link to the existing Python test
documentation.
Signed-off-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'doc/develop/py_testing.rst')
| -rw-r--r-- | doc/develop/py_testing.rst | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/doc/develop/py_testing.rst b/doc/develop/py_testing.rst index 7f01858cfd..c4cecc0a01 100644 --- a/doc/develop/py_testing.rst +++ b/doc/develop/py_testing.rst @@ -13,7 +13,8 @@ results. Advantages of this approach are: U-Boot; there can be no disconnect. - There is no need to write or embed test-related code into U-Boot itself. It is asserted that writing test-related code in Python is simpler and more - flexible than writing it all in C. + flexible than writing it all in C. But see :doc:`tests_writing` for caveats + and more discussion / analysis. - It is reasonably simple to interact with U-Boot in this way. Requirements |