From: Jens Axboe <axboe@kernel.dk>
To: Tomohiro Kusumi <kusumi.tomohiro@gmail.com>, fio@vger.kernel.org
Subject: Re: [PATCH 0/7] unittests: add CUnit based unittests
Date: Fri, 26 Oct 2018 10:27:45 -0600 [thread overview]
Message-ID: <908aad84-63d1-c2fa-6472-46ffdbde612f@kernel.dk> (raw)
In-Reply-To: <1540571746-12885-1-git-send-email-kusumi.tomohiro@gmail.com>
On 10/26/18 10:35 AM, Tomohiro Kusumi wrote:
> This series of patches introduce CUnit based unittests,
> plus fix bugs found in the test cases.
>
> CUnit is C version of *unit framework to help write test cases.
> https://sourceforge.net/projects/cunit/
>
> Having builtin unittest functionality for newly added code
> as well as exsiting code if possible helps prevent regression.
>
> Most of the code under lib/ and oslib/ (and os/) work as stand
> alone *.o files or inline functions with no dependencies on fio
> itself, so these are relatively easy to write unittests.
>
> Summary of patches
> 1/7: Add basic CUnit framework
> 2/7: Add unittest suite for lib/memalign.c as an example
> 3/7: Add unittest suite for lib/strntol.c as an example
> 4/7: Add unittest suite for oslib/strlcat.c as an example
> 5/7: Add unittest suite for oslib/strndup.c as an example
> 6/7: Fix lib/strntol.c which caused test failure in patch 3/7
> 7/7: Fix oslib/strlcat.c which caused test failure in patch 4/7
>
> Tomohiro Kusumi (7):
> unittests: add CUnit based unittest framework
> unittests: add unittest suite for lib/memalign.c
> unittests: add unittest suite for lib/strntol.c
> unittests: add unittest suite for oslib/strlcat.c
> unittests: add unittest suite for oslib/strndup.c
> lib: fix strntol's end pointer when str has leading spaces
> oslib: fix strlcat's incorrect copying
This is great! I've always wanted to get unit tests going, but
just never got around to it. This looks like a good start, and
simple enough to add more tests.
Applied, thanks!
--
Jens Axboe
next prev parent reply other threads:[~2018-10-26 16:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-26 16:35 [PATCH 0/7] unittests: add CUnit based unittests Tomohiro Kusumi
2018-10-26 16:27 ` Jens Axboe [this message]
2018-10-26 16:35 ` [PATCH 1/7] unittests: add CUnit based unittest framework Tomohiro Kusumi
2018-10-26 16:35 ` [PATCH 2/7] unittests: add unittest suite for lib/memalign.c Tomohiro Kusumi
2018-10-26 16:35 ` [PATCH 3/7] unittests: add unittest suite for lib/strntol.c Tomohiro Kusumi
2018-10-26 16:35 ` [PATCH 4/7] unittests: add unittest suite for oslib/strlcat.c Tomohiro Kusumi
2018-10-26 16:35 ` [PATCH 5/7] unittests: add unittest suite for oslib/strndup.c Tomohiro Kusumi
2018-10-26 16:35 ` [PATCH 6/7] lib: fix strntol's end pointer when str has leading spaces Tomohiro Kusumi
2018-10-26 16:35 ` [PATCH 7/7] oslib: fix strlcat's incorrect copying Tomohiro Kusumi
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=908aad84-63d1-c2fa-6472-46ffdbde612f@kernel.dk \
--to=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
--cc=kusumi.tomohiro@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