From: ismo@iki.fi (Ismo Puustinen)
Subject: [sup-talk] Unit tests
Date: Wed, 12 Dec 2007 22:51:11 +0200 [thread overview]
Message-ID: <1197492534-sup-9762@arlanda> (raw)
Hello,
I would like to contribute to Sup development by writing some unit
tests. In addition to the normal benefits (refactoring, regression
catching, documentation) the tests might help the Sup community
to report bugs: a backtrace isn't as helpful as a unit test that
deterministically leads to a failed assert or a crash. :-)
I wrote the first test (patch attached) to test the message.rb
file. The tests are run by simply saying "rake test" in the Sup
source code root directory. If you feel that unit tests might
prove useful, I'll be happy to write some more of them.
--
Ismo Puustinen <ismo at iki.fi>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: unit_test.diff
Type: application/octet-stream
Size: 12417 bytes
Desc: not available
Url : http://rubyforge.org/pipermail/sup-talk/attachments/20071212/8dd49550/attachment.obj
reply other threads:[~2007-12-12 20:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1197492534-sup-9762@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