Mailing-List: contact geronimo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: geronimo-dev@incubator.apache.org
Content-Class: urn:content-classes:message
Subject: RE: Starting writing testcases
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Importance: normal
Priority: normal
Content-Transfer-Encoding: quoted-printable
Date: Sat, 15 Nov 2003 13:16:59 -0000
Message-ID: <F1CE4737D64A1D4ABAC71CB4ACD2D8EA552AEF@salentino.edina.co.uk>
Thread-Topic: Starting writing testcases
thread-index: AcOrII7+ZKDUtNc5SzSPwwzly+0IQwAVs65w
From: "Jesse Beaumont" <Jesse.Beaumont@edina.co.uk>
To: <geronimo-dev@incubator.apache.org>

Hi,

Siva, Cian and myself are all working in the core module just now.  I
started with o.a.g.client tests and have now done the first cut (I had
to leave out o.a.g.client.Launcher for now because I can't figure out
how to test the main method satisfactorily since it calls System.exit on
error) so will be submitting that soon. =20
Last I heard Siva was working on o.a.g.xml.deployment and Cian was going
to start with o.a.g.ejb and work down (correct me if I'm wrong, guys)

Incidentally, questions to one/all of the committers,=20

a) when adding new files do you want a cvs diff (I don't know if cvs
diff picks up local-only files) or just the files?

b) the website (somewhere) states that code should be submitted to the
mailing list, but looking at jira it looks like people have been posting
it there, is that the preferred option?  If so the website should
probably be updated with new instructions.

One other point about the use of assert.  Has it been assumed that all
code and tests will be executed with assertion checking enabled?  It
becomes very difficult to write tests for assertions unless we assume
that because turning assertion checking off will cause assertion based
tests to fail.  For the time being I have just left out tests for the
assertions which in theory is fine except that the clover report does
not show as complete because of it.

Jesse

-----Original Message-----
From: Mujibur Rahman Shaik [mailto:mujiburrahman_shaik@yahoo.com]=20
Sent: 15 November 2003 02:31
To: geronimo-dev@incubator.apache.org
Subject: RE: Starting writing testcases

Hi siva and cian,

  Is there any location/page where the i can find who
is working on what. So that i can choose another
module to work. Iam currently looking at JMX and
related JSRs. Iam planning to start writing unit test
cases. It will be great, if we all work together and
cover all the modules.

Thanks
S.M.Rahman


--- cian <cian_oconnor@yahoo.co.uk> wrote:
> Hi Siva,
>=20
> That seems like a good idea.
>=20
> The easiest way to do this is for us to continue
> working on the packages
> we've self-assigned, then each time we finish the
> tests for a package, we
> inform the others, get the new test cases patched
> into the repository - then
> inform the others of the new package that we will be
> working on.
>=20
> Cheers,
> Cian
>=20
> -----Original Message-----
> From: Siva [mailto:siva@sella.it]
> Sent: Thursday, November 13, 2003 9:41 AM
> To: geronimo-dev@incubator.apache.org
> Subject: RE: Starting writing testcases
>=20
>=20
> Hi Cian,
>=20
>  Presently I am also into the core module,working on
> the o.a.g.x.deployment
> package.May be we should all work together and
> increase the test coverage
> for the core module and then progress to other
> modules.
>   Regarding clover,you can get a free license for
> usage in open source
> projects.For more details,see
> http://www.thecortex.net/clover/freelicense.jsp
>=20
> Ciao
> Siva
>=20


__________________________________
Do you Yahoo!?
Protect your identity with Yahoo! Mail AddressGuard
http://antispam.yahoo.com/whatsnewfree

---  Disclaimer  ---

Unless otherwise agreed expressly in writing by a Director of Edina =
Software, this communication is to be treated as confidential and the =
information in it may not be used or disclosed except for the purpose =
for which it has been sent. If you have reason to believe that you are =
not the intended recipient of this communication, please contact the =
sender immediately.