Re: [RFC PATCH v3 1/1] unit tests: Add a project plan document

From: Josh Steadmon <steadmon@google.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, calvinwan@google.com, szeder.dev@gmail.com,
	phillip.wood123@gmail.com, chooglen@google.com, avarab@gmail.com,
	sandals@crustytoothpaste.net
Subject: Re: [RFC PATCH v3 1/1] unit tests: Add a project plan document
Date: Fri, 30 Jun 2023 15:18:37 -0700	[thread overview]
Message-ID: <ZJ9UvXsZKQh+PFoV@google.com> (raw)
In-Reply-To: <xmqq7cs73sic.fsf@gitster.g>

On 2023.06.13 15:30, Junio C Hamano wrote:
> Josh Steadmon <steadmon@google.com> writes:
> 
> > In our current testing environment, we spend a significant amount of
> > effort crafting end-to-end tests for error conditions that could easily
> > be captured by unit tests (or we simply forgo some hard-to-setup and
> > rare error conditions).Describe what we hope to accomplish by
> > implementing unit tests, and explain some open questions and milestones.
> > Discuss desired features for test frameworks/harnesses, and provide a
> > preliminary comparison of several different frameworks.
> >
> > Signed-off-by: Josh Steadmon <steadmon@google.com>
> > Coauthored-by: Calvin Wan <calvinwan@google.com>
> > ---
> 
> The co-author should also signal his acceptance of the D-C-O with
> his own S-o-b.  [*1*] gives a good example.

Fixed in V4. Thanks.