From: "Meskauskas Audrius" <audriusa@bluewin.ch>
To: <mauve-discuss@sources.redhat.com>
Subject: Discussing a helper class to migrate from JUnit
Date: Sat, 29 Jan 2005 17:03:00 -0000 [thread overview]
Message-ID: <001701c50624$43f8df20$2101a8c0@computername> (raw)
Hello,
Following the rules of the Mauve project, I would like to discuss the
following addition to Mauve before submission:
Motivation:
JUnit is another popular testing suite. Some people may already have a
JUnit tests written and need to adapt them for Mauve. Some code generators
produce tests for JUnit and not for Mauve. In this context, it seems good to
have an additional helper class for easier conversion of JUnit TestCase into
Mauve Testlet. It is possible to have the individual helper class as a part
of the test itself. However it may be better to have it in a more public
place where it could be shared.
Suggestion:
1. The JUnit TestCase calls static methods like assertTrue(..),
assertEquals(..) and so on. The helper class can have the identically named
non-static methods, just delegating the call to the current instance of
TestHarness.
2. The JUnit TestCase has a multiple public non static parameterless
methods, starting with test.... These methods are found and called using
reflection. The helper class can do just the same.
3. The two protected methods, setUp() and tearDown(), should be present in a
helper class as they are frequently
called from the generated code. These two methods can return without action
for beginning.
The class, implementing these two things, would allow to run a typical JUnit
test on Mauve with only minor changes.
If no suggested otherwise, the class could be called Unitizer and placed
into gnu.testlet.
Regards
Audrius
next reply other threads:[~2005-01-29 17:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-29 17:03 Meskauskas Audrius [this message]
2005-01-30 15:59 ` Robert Schuster
2005-01-30 16:11 ` Thomas Zander
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='001701c50624$43f8df20$2101a8c0@computername' \
--to=audriusa@bluewin.ch \
--cc=mauve-discuss@sources.redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).