From: "René Scharfe" <l.s.r@web.de>
To: Jeff King <peff@peff.net>
Cc: Git Mailing List <git@vger.kernel.org>,
Junio C Hamano <gitster@pobox.com>,
Derrick Stolee <stolee@gmail.com>,
Eric Sunshine <sunshine@sunshineco.com>
Subject: Re: [PATCH RESEND] t4015: improve coverage of function context test
Date: Thu, 19 Dec 2019 18:35:28 +0100 [thread overview]
Message-ID: <7d454f2e-eaf6-1897-d6f6-c2e3e2a1f75f@web.de> (raw)
In-Reply-To: <20191218201241.GA6452@coredump.intra.peff.net>
Am 18.12.19 um 21:12 schrieb Jeff King:
> On Wed, Dec 18, 2019 at 07:05:54PM +0100, René Scharfe wrote:
>
>> Include an actual function line in the test files to check if context is
>> expanded to include the whole function, and add an ignored change before
>> function context to check if that one stays hidden, while the originally
>> ignored change within function context is shown.
>>
>> [...]
>> test_expect_success 'combine --ignore-blank-lines with --function-context' '
>> - test_write_lines 1 "" 2 3 4 5 >a &&
>> - test_write_lines 1 2 3 4 >b &&
>> + test_write_lines 1 2 3 "" function 1 2 3 4 5 "" 6 7 8 9 >a &&
>> + test_write_lines "" 1 2 3 "" function 1 2 3 4 5 6 7 8 >b &&
>
> I'm a little mixed on this one. This _is_ a much better test of how the
> two features should be have together. But I think the reason the
> original was so short was that it was added when fixing a bug where we'd
> iterate off the beginning of list of lines, which now no longer happens.
That fix, b777f3fd61 (xdiff: clamp function context indices in post-image,
2019-07-23), should no longer be necessary, but I didn't check that
thoroughly. Since we still have it (and I don't intend to remove it,
better keep that extra safety), it makes sense to keep the specific test.
> Maybe we should cover both cases in two separate tests?
That's easy enough to do. The hardest part is coming up with a name, but
simply counting up should do the trick here.
> I'd also suggest using "a b c" for the first three lines to avoid
> confusion (I don't think it's important that they're the same as the
> lines inside the "function").
Good point. That turns the last line into a function line, though, which
is unnecessary and confused me a bit, but I think it's a net win.
René
next prev parent reply other threads:[~2019-12-19 17:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-18 18:05 [PATCH RESEND] t4015: improve coverage of function context test René Scharfe
2019-12-18 20:12 ` Jeff King
2019-12-19 17:35 ` René Scharfe [this message]
2019-12-19 17:35 ` [PATCH v2] " René Scharfe
2019-12-19 17:51 ` Jeff King
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7d454f2e-eaf6-1897-d6f6-c2e3e2a1f75f@web.de \
--to=l.s.r@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=stolee@gmail.com \
--cc=sunshine@sunshineco.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).