linux-kselftest.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tales Aparecida <tales.aparecida@gmail.com>
To: Sadiya Kazi <sadiyakazi@google.com>,
	brendanhiggins@google.com, corbet@lwn.net
Cc: Trevor Woerner <twoerner@gmail.com>,
	siqueirajordao@riseup.net, mwen@igalia.com,
	andrealmeid@riseup.net, mairacanal@riseup.net,
	Isabella Basso <isabbasso@riseup.net>,
	magalilemes00@gmail.com, tales.aparecida@gmail.com,
	linux-kselftest@vger.kernel.org, kunit-dev@googlegroups.com,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 4/4] Documentation: Kunit: Add ref for other kinds of tests
Date: Sat, 13 Aug 2022 01:20:55 -0300	[thread overview]
Message-ID: <20220813042055.136832-5-tales.aparecida@gmail.com> (raw)
In-Reply-To: <20220813042055.136832-1-tales.aparecida@gmail.com>

Add an organic link to the "other kinds of tests" in the index page

Signed-off-by: Tales Aparecida <tales.aparecida@gmail.com>
---
 Documentation/dev-tools/kunit/faq.rst   | 2 ++
 Documentation/dev-tools/kunit/index.rst | 2 ++
 2 files changed, 4 insertions(+)

diff --git a/Documentation/dev-tools/kunit/faq.rst b/Documentation/dev-tools/kunit/faq.rst
index f1b4cef68ced..fae426f2634a 100644
--- a/Documentation/dev-tools/kunit/faq.rst
+++ b/Documentation/dev-tools/kunit/faq.rst
@@ -39,6 +39,8 @@ more work than using KUnit on UML.
 
 For more information, see :ref:`kunit-on-non-uml`.
 
+.. _kinds-of-tests:
+
 What is the difference between a unit test and other kinds of tests?
 ====================================================================
 Most existing tests for the Linux kernel would be categorized as an integration
diff --git a/Documentation/dev-tools/kunit/index.rst b/Documentation/dev-tools/kunit/index.rst
index 595205348d2d..bc91ad7b8961 100644
--- a/Documentation/dev-tools/kunit/index.rst
+++ b/Documentation/dev-tools/kunit/index.rst
@@ -95,6 +95,8 @@ Unit Testing Advantages
 - Improves code quality.
 - Encourages writing testable code.
 
+Read also :ref:`kinds-of-tests`.
+
 How do I use it?
 ================
 
-- 
2.37.1


  parent reply	other threads:[~2022-08-13  4:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-13  4:20 [PATCH 0/4] Documentation: KUnit: minor fixes Tales Aparecida
2022-08-13  4:20 ` [PATCH 1/4] Documentation: kunit: fix trivial typo Tales Aparecida
2022-08-13  7:03   ` David Gow
2022-08-17  6:41   ` Sadiya Kazi
2022-08-13  4:20 ` [PATCH 2/4] Documentation: Kunit: Fix inconsistent titles Tales Aparecida
2022-08-13  7:04   ` David Gow
2022-08-17  6:46   ` Sadiya Kazi
2022-08-13  4:20 ` [PATCH 3/4] Documentation: KUnit: Fix non-uml anchor Tales Aparecida
2022-08-13  7:04   ` David Gow
2022-08-13  4:20 ` Tales Aparecida [this message]
2022-08-13  7:04   ` [PATCH 4/4] Documentation: Kunit: Add ref for other kinds of tests David Gow
2022-08-15 16:51 ` [PATCH 0/4] Documentation: KUnit: minor fixes André Almeida
2022-08-18 18:20 ` Tales Lelo da Aparecida

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220813042055.136832-5-tales.aparecida@gmail.com \
    --to=tales.aparecida@gmail.com \
    --cc=andrealmeid@riseup.net \
    --cc=brendanhiggins@google.com \
    --cc=corbet@lwn.net \
    --cc=isabbasso@riseup.net \
    --cc=kunit-dev@googlegroups.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=magalilemes00@gmail.com \
    --cc=mairacanal@riseup.net \
    --cc=mwen@igalia.com \
    --cc=sadiyakazi@google.com \
    --cc=siqueirajordao@riseup.net \
    --cc=twoerner@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).