From: Calvin Wan <calvinwan@google.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [RFC PATCH 0/2] add an external testing library for unit tests
Date: Thu, 27 Apr 2023 11:46:36 -0700 [thread overview]
Message-ID: <CAFySSZAXLnPjndDpXeUK9x1ZK_OuCPV+DyuHSC6O7=3oYx68Vw@mail.gmail.com> (raw)
In-Reply-To: <xmqqr0s5jhj4.fsf@gitster.g>
On Thu, Apr 27, 2023 at 11:40 AM Junio C Hamano <gitster@pobox.com> wrote:
>
> Calvin Wan <calvinwan@google.com> writes:
>
> > ... Unit tests additionally provide stability to the
> > codebase and can simplify debugging through isolation. Turning parts of
> > Git into libraries[1] gives us the ability to run unit tests on the
> > libraries and to write unit tests in C. Writing unit tests in pure C,
> > rather than with our current shell/test-tool helper setup, simplifies
> > test setup, simplifies passing data around (no shell-isms required), and
> > reduces testing runtime by not spawning a separate process for every
> > test invocation.
>
> Good goal, except that unit tests are not panacea---our ultimate
> obligation is to give a stable behaviour to the end users and
> end-to-end testing is still needed. We would benefit from having
> tests at both levels.
Ah I seem to have misworded this section a bit. I didn't mean to say
that writing unit tests in C would replace our current shell/test-tool
setup. I meant to make the comparison between writing unit tests in C
vs writing unit tests with our current shell/test-tool setup. And I
agree that we would benefit from having
tests at both levels.
next prev parent reply other threads:[~2023-04-27 18:46 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-27 17:50 [RFC PATCH 0/2] add an external testing library for unit tests Calvin Wan
2023-04-27 17:50 ` [RFC PATCH 1/2] Add C TAP harness Calvin Wan
2023-04-27 18:29 ` SZEDER Gábor
2023-04-27 18:38 ` Calvin Wan
2023-04-27 20:15 ` Phillip Wood
2023-04-28 16:31 ` Calvin Wan
2023-05-02 15:46 ` Felipe Contreras
2023-05-10 15:46 ` Phillip Wood
2023-05-11 23:16 ` Glen Choo
2023-05-18 10:04 ` Phillip Wood
2023-06-21 15:57 ` Linus Arver
2023-06-26 13:15 ` Phillip Wood
2023-06-28 21:17 ` Linus Arver
2023-06-29 5:52 ` Oswald Buddenhagen
2023-06-30 9:48 ` Phillip Wood
2023-05-02 15:54 ` Felipe Contreras
2023-05-02 16:39 ` Ævar Arnfjörð Bjarmason
2023-05-02 18:11 ` Felipe Contreras
2023-05-02 16:34 ` Ævar Arnfjörð Bjarmason
2023-05-10 8:18 ` Phillip Wood
2023-04-27 17:50 ` [RFC PATCH 2/2] unit test: add basic example Calvin Wan
2023-04-27 18:47 ` Junio C Hamano
2023-05-02 15:58 ` Felipe Contreras
2023-04-27 18:39 ` [RFC PATCH 0/2] add an external testing library for unit tests Junio C Hamano
2023-04-27 18:46 ` Calvin Wan [this message]
2023-04-27 21:35 ` brian m. carlson
2023-05-02 4:18 ` Felipe Contreras
2023-05-02 13:52 ` Ævar Arnfjörð Bjarmason
2023-05-02 15:28 ` Felipe Contreras
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='CAFySSZAXLnPjndDpXeUK9x1ZK_OuCPV+DyuHSC6O7=3oYx68Vw@mail.gmail.com' \
--to=calvinwan@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).