[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGS_qxo63enQyrEO7YOL75oGUsuzbntty-C60Z+==L59qKyBtw@mail.gmail.com>
Date: Mon, 10 Jan 2022 14:25:05 -0800
From: Daniel Latypov <dlatypov@...gle.com>
To: Brendan Higgins <brendanhiggins@...gle.com>
Cc: davidgow@...gle.com, linux-kernel@...r.kernel.org,
kunit-dev@...glegroups.com, linux-kselftest@...r.kernel.org,
skhan@...uxfoundation.org, torvalds@...ux-foundation.org
Subject: Re: [PATCH 1/6] kunit: add example test case showing off all the
expect macros
On Mon, Jan 10, 2022 at 2:14 PM Brendan Higgins
<brendanhiggins@...gle.com> wrote:
>
> On Fri, Jan 7, 2022 at 8:23 PM Daniel Latypov <dlatypov@...gle.com> wrote:
> >
> > 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@...gle.com>
>
> I still don't like how much this bloats the example test; aside from
> that, this looks good.
Agreed, it does add bloat.
I just wanted something *somewhere* I could use to smoketest the later changes.
I just remembered how people weren't very aware of the _MSG variants
and thought this could help.
If others have a preference, I'll happily move out and into kunit-test.c.
I'm fine either way as I initially was going to put it there to begin with.
>
> Reviewed-by: Brendan Higgins <brendanhiggins@...gle.com>
Powered by blists - more mailing lists