unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Tomi Ollila <tomi.ollila@iki.fi>
To: Aaron Ecay <aaronecay@gmail.com>, notmuch@notmuchmail.org
Subject: Re: [PATCH] test/README: mention the test_expect_equal_json and *sanitize* functions
Date: Wed, 06 Mar 2013 10:34:12 +0200	[thread overview]
Message-ID: <m2ppzd3p17.fsf@guru.guru-group.fi> (raw)
In-Reply-To: <1362540882-1894-1-git-send-email-aaronecay@gmail.com>

On Wed, Mar 06 2013, Aaron Ecay <aaronecay@gmail.com> wrote:

> also fix one typo
> ---

LGTM.

Tomi


>  test/README | 22 +++++++++++++++++++++-
>  1 file changed, 21 insertions(+), 1 deletion(-)
>
> diff --git a/test/README b/test/README
> index 81c232d..d12cff2 100644
> --- a/test/README
> +++ b/test/README
> @@ -178,11 +178,18 @@ library for your script to use.
>  
>   test_expect_equal_file <file1> <file2>
>  
> -   Identical to test_exepect_equal, except that <file1> and <file2>
> +   Identical to test_expect_equal, except that <file1> and <file2>
>     are files instead of strings.  This is a much more robust method to
>     compare formatted textual information, since it also notices
>     whitespace and closing newline differences.
>  
> + test_expect_equal_json <output> <expected>
> +
> +   Identical to test_expect_equal, except that the two strings are
> +   treated as JSON and canonicalized before equality testing.  This is
> +   useful to abstract away from whitespace differences in the expected
> +   output and that generated by running a notmuch command.
> +
>   test_debug <script>
>  
>     This takes a single argument, <script>, and evaluates it only
> @@ -253,3 +260,16 @@ variables which are useful in writing tests:
>      generated script that should be called instead of notmuch to do
>      the counting.  The notmuch_counter_value() function prints the
>      current counter value.
> +
> +There are also functions which remove various environment-dependent
> +values from notmuch output; these are useful to ensure that test
> +results remain consistent across different machines.
> +
> + notmuch_search_sanitize
> + notmuch_show_sanitize
> + notmuch_show_sanitize_all
> + notmuch_json_show_sanitize
> +
> +   All these functions should receive the text to be sanitized as the
> +   input of a pipe, e.g.
> +   output=`notmuch search "..." | notmuch_search_sanitize`
> -- 
> 1.8.1.5
>
> _______________________________________________
> notmuch mailing list
> notmuch@notmuchmail.org
> http://notmuchmail.org/mailman/listinfo/notmuch

  reply	other threads:[~2013-03-06  8:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-06  3:34 [PATCH] test/README: mention the test_expect_equal_json and *sanitize* functions Aaron Ecay
2013-03-06  8:34 ` Tomi Ollila [this message]
2013-03-07 13:48 ` David Bremner

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: https://notmuchmail.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m2ppzd3p17.fsf@guru.guru-group.fi \
    --to=tomi.ollila@iki.fi \
    --cc=aaronecay@gmail.com \
    --cc=notmuch@notmuchmail.org \
    /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://yhetil.org/notmuch.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).