[PATCH] test/README: mention the test_expect_equal_json and *sanitize* functions

2013-03-05 Thread Aaron Ecay
also fix one typo
---
 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  

-   Identical to test_exepect_equal, except that  and 
+   Identical to test_expect_equal, except that  and 
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  
+
+   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 

[PATCH] test/README: mention the test_expect_equal_json and *sanitize* functions

2013-03-06 Thread Tomi Ollila
On Wed, Mar 06 2013, Aaron Ecay  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  
>  
> -   Identical to test_exepect_equal, except that  and 
> +   Identical to test_expect_equal, except that  and 
> 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  
> +
> +   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 

[PATCH] test/README: mention the test_expect_equal_json and *sanitize* functions

2013-03-07 Thread David Bremner
Aaron Ecay  writes:

> also fix one typo
> ---

pushed,

d


Re: [PATCH] test/README: mention the test_expect_equal_json and *sanitize* functions

2013-03-06 Thread Tomi Ollila
On Wed, Mar 06 2013, Aaron Ecay  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  
>  
> -   Identical to test_exepect_equal, except that  and 
> +   Identical to test_expect_equal, except that  and 
> 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  
> +
> +   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 

Re: [PATCH] test/README: mention the test_expect_equal_json and *sanitize* functions

2013-03-07 Thread David Bremner
Aaron Ecay  writes:

> also fix one typo
> ---

pushed,

d
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch