From: ismo@iki.fi (Ismo Puustinen)
Subject: [sup-talk] Unit tests, part 2
Date: Sat, 15 Dec 2007 20:25:35 +0200 [thread overview]
Message-ID: <1197741811-sup-1386@arlanda> (raw)
Hi,
I wrote one new unit test. The difference to previous tests is that
this test actually currently fails: for some reason, dividing a
message body into chunks doesn't succeed. The message in question
is an actual email message sent to vim-mac mailing list; only
the names and email addresses have been obscured. I selected the
message for the tests because it kept crashing my sup-sync. :-)
As the previous unit tests haven't been accepted to the svn, I
made a new patch of the whole "test" directory (attached). In order
to run the tests, just say "rake test" in the source directory.
--
Ismo Puustinen <ismo at iki.fi>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: tests-2.patch
Type: application/octet-stream
Size: 16127 bytes
Desc: not available
Url : http://rubyforge.org/pipermail/sup-talk/attachments/20071215/255e8466/attachment.obj
next reply other threads:[~2007-12-15 18:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-15 18:25 Ismo Puustinen [this message]
2008-01-04 5:04 ` William Morgan
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1197741811-sup-1386@arlanda \
--to=ismo@iki.fi \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox