From: Felipe Contreras <felipe.contreras@gmail.com>
To: notmuch@notmuchmail.org
Subject: [PATCH] test/search: add check for slightly trick search
Date: Sun, 6 Feb 2011 15:21:13 +0200 [thread overview]
Message-ID: <1296998473-13514-1-git-send-email-felipe.contreras@gmail.com> (raw)
It's not really tricky, there are many addresses with a '-' in them. I
personally really want to differentiate between foo, foo-testing, and
foo-patches.
This fails, but it shouldn't:
FAIL Search by from (tricky):
--- search.17.expected 2011-02-06 13:16:31.871509560 +0000
+++ search.17.output 2011-02-06 13:16:31.871509560 +0000
@@ -1 +1,3 @@
+thread:XXX 2000-01-01 [1/1] Search By From Name; search by from (name) (inbox unread)
+thread:XXX 2000-01-01 [1/1] search-by-from-trick; search by from (tricky trick) (inbox unread)
thread:XXX 2000-01-01 [1/1] search-by-from; search by from (tricky) (inbox unread)
Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>
---
test/search | 6 ++++++
1 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/test/search b/test/search
index b180c7f..ad5bbaa 100755
--- a/test/search
+++ b/test/search
@@ -123,4 +123,10 @@ echo -n > expected &&
notmuch search "no-message-matches-this" > actual &&
test_cmp expected actual'
+test_begin_subtest "Search by from (tricky):"
+add_message '[subject]="search by from (tricky trick)"' '[date]="Sat, 01 Jan 2000 12:00:00 -0000"' '[from]=search-by-from-trick'
+add_message '[subject]="search by from (tricky)"' '[date]="Sat, 01 Jan 2000 12:00:00 -0000"' '[from]=search-by-from'
+output=$(notmuch search from:'search-by-from' | notmuch_search_sanitize)
+test_expect_equal "$output" "thread:XXX 2000-01-01 [1/1] search-by-from; search by from (tricky) (inbox unread)"
+
test_done
--
1.7.4.1.g4f7e4.dirty
next reply other threads:[~2011-02-06 13:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-06 13:21 Felipe Contreras [this message]
2011-02-06 22:39 ` [PATCH] test/search: add check for slightly trick search Felipe Contreras
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=1296998473-13514-1-git-send-email-felipe.contreras@gmail.com \
--to=felipe.contreras@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).