I mixed with Emma - both of them of 4 chars :) http://emma.sourceforge.net
Mikhail On 2/16/06, Matthew Johnson <[EMAIL PROTECTED]> wrote: > JCSC is a Java Coding Standard Checker - ie, just conformance, not > coverage. There's a good list of code coverage tools at > http://java-source.net/open-source/code-coverage. > > > Matt > > > -----Original Message----- > > From: Mikhail Loenko [mailto:[EMAIL PROTECTED] > > Sent: Thursday, 16 February 2006 4:00 PM > > To: [email protected] > > Subject: Re: newbie to project-where to start from > > > > Hi Karan > > > > if there is some area that you are interesting in the most, you might > > want to say it and people who developed classes in that area > > could advise for which of them are untested. > > > > All, > > > > I think it makes sense to include into the build a target > > that calculates > > coverage - that would advise people where to contribute the tests. > > BTW, what do you think about JCSC coverage tool? > > http://jcsc.sourceforge.net/ > > > > Thanks, > > Mikhail > > > > > > On 2/16/06, karan malhi <[EMAIL PROTECTED]> wrote: > > > Tim, > > > > > > Thanks for such a detailed reply. I have a couple of more > > questions: > > > 1. Do I have to sign and fax back the questionnaire before I start > > > working on harmony ? > > > 2. I know this is dumb but I saw in some previous posts > > that the tests > > > were being compiled with jrockit. I guess I can use any > > compiler (sun) > > > without causing any licensing issues - right? Sorry, but I > > am very poor > > > with this licensing stuff. Just want to make sure I am > > playing within > > > the rules of the game. > > > > > > > > > Tim Ellison wrote: > > > > > > >karan malhi wrote: > > > > > > > > > > > >>I need to know how I can start on harmony. I would like > > to start by > > > >>writing some tests. > > > >> > > > >> > > > > > > > >That would be great -- thanks Karan! > > > > > > > >If you have detailed knowledge of another implementation > > of Java then we > > > >need to talk further, otherwise dive right in. Examples > > of 'detailed > > > >knowledge' can be found in the Harmony Questionnaire [0] > > > > > > > >[0] http://incubator.apache.org/harmony/auth_cont_quest.html > > > > > > > > > > > > > > > >>Here are my questions : > > > >>1. Are there any predefined assertions to test or do we > > simply write > > > >>test after looking at the api docs for each method > > > >> > > > >> > > > > > > > >Looking at the spec and writing tests is a pretty good > > start. There are > > > >some tests in the repository already, and some more > > incoming, but we'll > > > >worry about merging new code into the full test suite. > > > > > > > > > > > > > > > >>2. Are there any naming conventions for test cases > > > >> > > > >> > > > > > > > >Yes. > > > > > > > >Pick a module [1] that interests you and from there the > > test code is in > > > > > ><module_name>/src/test/java/org.apache.harmony.tests.<pkg>.<t > > ype>Test.java > > > >where <pkg> and <type> are the package and type under > > test; see here [2] > > > >for an example. > > > > > > > >We are using JUnit, so your test class extends > > junit.framework.TestCase. > > > > Each test method is "public void test_<methodID>()" where > > <methodID> is > > > >the method under test including param types; e.g. [3]. > > > > > > > >Don't worry too much about the names, we'll fix them on > > the way in if > > > >necessary. > > > > > > > >[1] > > > > > >http://svn.apache.org/viewcvs.cgi/incubator/harmony/enhanced/ > > classlib/trunk/modules/ > > > >[2] > > > > > >http://svn.apache.org/viewcvs.cgi/incubator/harmony/enhanced/ > classlib/trunk/modules/luni/src/test/java/org/apache/harmony/tests/java/ > net/ > > > >[3] > > > > > >http://svn.apache.org/viewcvs.cgi/incubator/harmony/enhanced/ > classlib/trunk/modules/luni/src/test/java/org/apache/harmony/tests/java/ > net/InetAddressT> est.java?view=markup > > > > > > > > > > > > > > > >>3. When one files a JIRA for a failed test, does one also > > attach the > > > >>test to the JIRA > > > >> > > > >> > > > > > > > >Yes please, a succinct description with a unit test is > > great, and if you > > > >have a proposed patch that would be even better ;-) > > > > > > > >We have had lots of good examples of bug reports, here's > > one I picked at > > > >random to show the type of thing we like to see: > > > > https://issues.apache.org/jira/browse/HARMONY-53 > > > > > > > >Thanks again for your offer of help. > > > > > > > >Regards, > > > >Tim > > > > > > > > > > > > > > > > > > -- > > > Karan Singh > > > > > > > > >
