From: Daniel Latypov <dlatypov@google.com>
To: brendanhiggins@google.com, davidgow@google.com
Cc: linux-kernel@vger.kernel.org, kunit-dev@googlegroups.com,
linux-kselftest@vger.kernel.org, skhan@linuxfoundation.org,
torvalds@linux-foundation.org,
Daniel Latypov <dlatypov@google.com>
Subject: [PATCH 1/6] kunit: add example test case showing off all the expect macros
Date: Fri, 7 Jan 2022 17:22:59 -0800 [thread overview]
Message-ID: <20220108012304.1049587-2-dlatypov@google.com> (raw)
In-Reply-To: <20220108012304.1049587-1-dlatypov@google.com>
Currently, these macros are only really documented near the bottom of
https://www.kernel.org/doc/html/latest/dev-tools/kunit/api/test.html#c.KUNIT_FAIL.
E.g. it's likely someone might just not realize that
KUNIT_EXPECT_STREQ() exists and instead use KUNIT_EXPECT_FALSE(strcmp())
or similar.
This can also serve as a basic smoketest that the KUnit assert machinery
still works for all the macros.
Signed-off-by: Daniel Latypov <dlatypov@google.com>
---
lib/kunit/kunit-example-test.c | 46 ++++++++++++++++++++++++++++++++++
1 file changed, 46 insertions(+)
diff --git a/lib/kunit/kunit-example-test.c b/lib/kunit/kunit-example-test.c
index 51099b0ca29c..182a64c12541 100644
--- a/lib/kunit/kunit-example-test.c
+++ b/lib/kunit/kunit-example-test.c
@@ -69,6 +69,51 @@ static void example_mark_skipped_test(struct kunit *test)
/* This line should run */
kunit_info(test, "You should see this line.");
}
+
+/*
+ * This test shows off all the KUNIT_EXPECT macros.
+ */
+static void example_all_expect_macros_test(struct kunit *test)
+{
+ KUNIT_EXPECT_TRUE(test, true);
+ KUNIT_EXPECT_FALSE(test, false);
+
+ KUNIT_EXPECT_EQ(test, 1, 1);
+ KUNIT_EXPECT_GE(test, 1, 1);
+ KUNIT_EXPECT_LE(test, 1, 1);
+ KUNIT_EXPECT_NE(test, 1, 0);
+ KUNIT_EXPECT_GT(test, 1, 0);
+ KUNIT_EXPECT_LT(test, 0, 1);
+
+ KUNIT_EXPECT_NOT_ERR_OR_NULL(test, test);
+ KUNIT_EXPECT_PTR_EQ(test, NULL, NULL);
+ KUNIT_EXPECT_PTR_NE(test, test, NULL);
+
+ KUNIT_EXPECT_STREQ(test, "hi", "hi");
+ KUNIT_EXPECT_STRNEQ(test, "hi", "bye");
+
+ /*
+ * There are also _MSG variants of all of the above that let you include
+ * additional text on failure.
+ */
+ KUNIT_EXPECT_TRUE_MSG(test, true, "msg");
+ KUNIT_EXPECT_FALSE_MSG(test, false, "msg");
+
+ KUNIT_EXPECT_EQ_MSG(test, 1, 1, "msg");
+ KUNIT_EXPECT_GE_MSG(test, 1, 1, "msg");
+ KUNIT_EXPECT_LE_MSG(test, 1, 1, "msg");
+ KUNIT_EXPECT_NE_MSG(test, 1, 0, "msg");
+ KUNIT_EXPECT_GT_MSG(test, 1, 0, "msg");
+ KUNIT_EXPECT_LT_MSG(test, 0, 1, "msg");
+
+ KUNIT_EXPECT_NOT_ERR_OR_NULL_MSG(test, test, "msg");
+ KUNIT_EXPECT_PTR_EQ_MSG(test, NULL, NULL, "msg");
+ KUNIT_EXPECT_PTR_NE_MSG(test, test, NULL, "msg");
+
+ KUNIT_EXPECT_STREQ_MSG(test, "hi", "hi", "msg");
+ KUNIT_EXPECT_STRNEQ_MSG(test, "hi", "bye", "msg");
+}
+
/*
* Here we make a list of all the test cases we want to add to the test suite
* below.
@@ -83,6 +128,7 @@ static struct kunit_case example_test_cases[] = {
KUNIT_CASE(example_simple_test),
KUNIT_CASE(example_skip_test),
KUNIT_CASE(example_mark_skipped_test),
+ KUNIT_CASE(example_all_expect_macros_test),
{}
};
--
2.34.1.575.g55b058a8bb-goog
next prev parent reply other threads:[~2022-01-08 1:23 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-08 1:22 [PATCH 0/6] kunit: refactor assertions to use less stack Daniel Latypov
2022-01-08 1:22 ` Daniel Latypov [this message]
2022-01-10 22:13 ` [PATCH 1/6] kunit: add example test case showing off all the expect macros Brendan Higgins
2022-01-10 22:25 ` Daniel Latypov
2022-01-11 6:50 ` David Gow
2022-01-11 17:27 ` Daniel Latypov
2022-01-08 1:23 ` [PATCH 2/6] kunit: move check if assertion passed into the macros Daniel Latypov
2022-01-10 22:21 ` Brendan Higgins
2022-01-10 22:32 ` Daniel Latypov
2022-01-11 6:51 ` David Gow
2022-01-11 18:42 ` Daniel Latypov
2022-01-08 1:23 ` [PATCH 3/6] kunit: drop unused kunit* field in kunit_assert Daniel Latypov
2022-01-10 22:24 ` Brendan Higgins
2022-01-11 6:51 ` David Gow
2022-01-11 18:34 ` Daniel Latypov
2022-01-08 1:23 ` [PATCH 4/6] kunit: factor out kunit_base_assert_format() call into kunit_fail() Daniel Latypov
2022-01-10 22:31 ` Brendan Higgins
2022-01-10 22:35 ` Daniel Latypov
2022-01-11 6:51 ` David Gow
2022-01-08 1:23 ` [PATCH 5/6] kunit: split out part of kunit_assert into a static const Daniel Latypov
2022-01-11 6:57 ` David Gow
2022-01-11 17:07 ` Daniel Latypov
2022-01-08 1:23 ` [PATCH 6/6] kunit: drop unused assert_type from kunit_assert and clean up macros Daniel Latypov
2022-01-11 6:57 ` David Gow
2022-01-11 19:21 ` Daniel Latypov
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=20220108012304.1049587-2-dlatypov@google.com \
--to=dlatypov@google.com \
--cc=brendanhiggins@google.com \
--cc=davidgow@google.com \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=torvalds@linux-foundation.org \
/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
Powered by JetHome