From: David Gow <davidgow@google.com>
To: Rae Moar <rmoar@google.com>
Cc: shuah@kernel.org, dlatypov@google.com, brendan.higgins@linux.dev,
sadiyakazi@google.com, keescook@chromium.org, arnd@arndb.de,
linux-kselftest@vger.kernel.org, linux-arch@vger.kernel.org,
kunit-dev@googlegroups.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 3/6] kunit: add example suite to test init suites
Date: Thu, 14 Dec 2023 11:04:52 +0800 [thread overview]
Message-ID: <CABVgOSk-6mmHTK4K1FfdEC8pG0HDPAttOxm-ziFJYspDwn_OPA@mail.gmail.com> (raw)
In-Reply-To: <20231213194421.2031671-3-rmoar@google.com>
[-- Attachment #1: Type: text/plain, Size: 2189 bytes --]
On Thu, 14 Dec 2023 at 03:44, Rae Moar <rmoar@google.com> wrote:
>
> Add example_init_test_suite to allow for testing the feature of running
> test suites marked as init to indicate they use init data and/or
> functions.
>
> This suite should always pass and uses a simple init function.
>
> This suite can also be used to test the is_init attribute introduced in
> the next patch.
>
> Signed-off-by: Rae Moar <rmoar@google.com>
> ---
Thanks -- this looks better to me.
Reviewed-by: David Gow <davidgow@google.com>
-- David
> Changes since v4:
> - Mark test as __init and then set cases as __refdata to supress modpost
> warnings
>
> lib/kunit/kunit-example-test.c | 37 ++++++++++++++++++++++++++++++++++
> 1 file changed, 37 insertions(+)
>
> diff --git a/lib/kunit/kunit-example-test.c b/lib/kunit/kunit-example-test.c
> index 6bb5c2ef6696..d2f7a3c62c18 100644
> --- a/lib/kunit/kunit-example-test.c
> +++ b/lib/kunit/kunit-example-test.c
> @@ -287,4 +287,41 @@ static struct kunit_suite example_test_suite = {
> */
> kunit_test_suites(&example_test_suite);
>
> +static int __init init_add(int x, int y)
> +{
> + return (x + y);
> +}
> +
> +/*
> + * This test should always pass. Can be used to test init suites.
> + */
> +static void __init example_init_test(struct kunit *test)
> +{
> + KUNIT_EXPECT_EQ(test, init_add(1, 1), 2);
> +}
> +
> +/*
> + * The kunit_case struct cannot be marked as __initdata as this will be
> + * used in debugfs to retrieve results after test has run
> + */
> +static struct kunit_case __refdata example_init_test_cases[] = {
> + KUNIT_CASE(example_init_test),
> + {}
> +};
> +
> +/*
> + * The kunit_suite struct cannot be marked as __initdata as this will be
> + * used in debugfs to retrieve results after test has run
> + */
> +static struct kunit_suite example_init_test_suite = {
> + .name = "example_init",
> + .test_cases = example_init_test_cases,
> +};
> +
> +/*
> + * This registers the test suite and marks the suite as using init data
> + * and/or functions.
> + */
> +kunit_test_init_section_suites(&example_init_test_suite);
> +
> MODULE_LICENSE("GPL v2");
> --
> 2.43.0.472.g3155946c3a-goog
>
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4003 bytes --]
next prev parent reply other threads:[~2023-12-14 3:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 19:44 [PATCH v5 1/6] kunit: move KUNIT_TABLE out of INIT_DATA Rae Moar
2023-12-13 19:44 ` [PATCH v5 2/6] kunit: add KUNIT_INIT_TABLE to init linker section Rae Moar
2023-12-13 19:44 ` [PATCH v5 3/6] kunit: add example suite to test init suites Rae Moar
2023-12-14 3:04 ` David Gow [this message]
2023-12-13 19:44 ` [PATCH v5 4/6] kunit: add is_init test attribute Rae Moar
2023-12-13 19:44 ` [PATCH v5 5/6] kunit: add ability to run tests after boot using debugfs Rae Moar
2023-12-13 19:44 ` [PATCH v5 6/6] Documentation: Add debugfs docs with run after boot Rae Moar
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=CABVgOSk-6mmHTK4K1FfdEC8pG0HDPAttOxm-ziFJYspDwn_OPA@mail.gmail.com \
--to=davidgow@google.com \
--cc=arnd@arndb.de \
--cc=brendan.higgins@linux.dev \
--cc=dlatypov@google.com \
--cc=keescook@chromium.org \
--cc=kunit-dev@googlegroups.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=rmoar@google.com \
--cc=sadiyakazi@google.com \
--cc=shuah@kernel.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;
as well as URLs for NNTP newsgroup(s).