Re: GSoC 2016 | Proposal | Incremental Rewrite of git bisect
- From
Pranit Bauva <pranit.bauva@gmail.com>
- Date
- Mar 25, 2016, 11:43 UTC
- Message-ID
- <CAFZEwPPKE1kODzSD4ZqZOehSB2SUUAC5JF-j7__kA2obpV92Tw@mail.gmail.com>
- In-Reply-To
- <CAP8UFD0vm1Sn07ickfPz5segbM-M7+HR43CMMGsB9WTqj5s-yw@mail.gmail.com>
On Fri, Mar 25, 2016 at 5:10 PM, Christian Couder <christian.couder@gmail.com> wrote:
Show 14 quoted lines
> On Fri, Mar 25, 2016 at 11:15 AM, Pranit Bauva <pranit.bauva@gmail.com> wrote: >>> - you will add an option to "git bisect--helper" to perform what the >>> git-bisect.sh function did, and >>> - you will create a test script for "git bisect--helper" in which you >>> will test each option? >> >> I had very initially planned to do this. But Matthieu pointed out that >> it would be much better to use the existing test suite rather than >> creating one which can lead to less coverage. > > Ok, then perhaps: > > - you will add tests to existing test scripts, so that each "git > bisect--helper" option is (indirectly) tested.
Yes. I will mention this in the proposal also. Thanks for reminding.