Re: [PATCH v3 0/6] Move --no-exclude to --exclude=(true|false|flag)

[Jameson Graef Rollins <jrollins@finestructure.net>]

[-- Attachment #1: Type: text/plain, Size: 1358 bytes --]

On Fri, Apr 06 2012, Mark Walters <markwalters1009@gmail.com> wrote:
> There are some exclude tests for count in test/count. Do you think it
> needs to be a full test everything like in test/search-exclude?

Ah yes.  Somehow I missed that.

I might prefer to keep all exclude tests in one test script.  In which
case it would be good to move the count exclude tests there, and maybe
round it out by testing both exclude options.

> There aren't any tests for show exclude, but there aren't very many
> tests explicitly for show anyway. My preference would be to add
> something like
> id:"1332171061-27983-1-git-send-email-markwalters1009@gmail.com" and add
> some tests to that.

Oh wow I wonder why that hasn't been pushed yet.  That's a bunch of new
good tests.  It's a long changeset, which is probably why there aren't
any reviews, but it's all test additions so we should definitely
fast-track it.  I'll try to look at it this weekend.

> I could add some tests for show-excludes in the same format as the
> search-exclude tests though if you think that is better.

As I mentioned above, I personally think it would nice to test all the
exclude functionality in one test script.  So I would vote for adding
some show exclude tests there.  Definitely doesn't need to be as
exhaustive as the search tests, but at least covering both cli options.

jamie.

[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]