Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: pass (nike.apache.org: domain of hiranya911@gmail.com designates
 209.85.219.211 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=urusAdQU3rOThFpIc5yzvg/l/zaiOHqGp7yNNVWQw+oDmf9j/Jl5X1ueLUGxH4cYYc
         y0RBnhml4fXRsjOBVJSaaAO3ahAAq0zJfPqS/3JestCD5HshIb1ezSFG5Pw/B2p1ANOQ
         MBdwxX9+tSOXllmLDxFXy+dKZ+q1FojHguvUA=
MIME-Version: 1.0
In-Reply-To: <x1oxab1yz97l.fsf@sun.com>
References: <558af1840908162237x524d24f5n7639207f72a72c98@mail.gmail.com>
	 <x1oxab1yz97l.fsf@sun.com>
Date: Tue, 18 Aug 2009 11:05:16 +0530
Message-ID: <558af1840908172235m3c1c7088rdf06b52fced39958@mail.gmail.com>
Subject: Re: Derby Test Framework and New dblook Test
From: Hiranya Jayathilaka <hiranya911@gmail.com>
To: derby-dev@db.apache.org
Content-Type: multipart/alternative; boundary=0015174c141820276d047163e23d

--0015174c141820276d047163e23d
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

On Mon, Aug 17, 2009 at 10:08 PM, Dag H. Wanvik <Dag.Wanvik@sun.com> wrote:

>
> Hi Hiranya,
>
> Hiranya Jayathilaka <hiranya911@gmail.com> writes:
>
> > Hi Folks,
> >
> > I'm in the middle of writing the new tests for dblook. When going through
> > the existing dblook tests I realized that they are not junit tests. Some
> of
> > the test classes have main methods. So I was wondering how should I
> organize
> > the new tests. Should they be written as junit tests or should they be
> > similar to the existing tests?
>
>
> I had forgotten the old dblook tests were not in JUnit :( Converting
> those adds a not insignificant extra amount of work for you..
>
> Maybe you could first build the new tests in JUnit, and if you have
> time, convert the old test cases at the end of your effort,


+1. That's what I had in mind too.

Thanks,
Hiranya


> maybe the
> old tests will be fully superceded by your tests in any case.
>
> If you think converting the old tests will definitely be too much work
> given the time remaining, augmenting the present tests is also
> acceptable, I think. The community could convert them to JUnit
> later. I think it is more important that you get new tests in at all,
> than what format they are in.
>
> Obviously, we would prefer JUnit ;-) since we are trying to get rid of
> the canon based tests.
>
> Thanks again for your efforts!
>
> Dag
>

--0015174c141820276d047163e23d
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br><br><div class=3D"gmail_quote">On Mon, Aug 17, 2009 at 10:08 PM, Dag H.=
 Wanvik <span dir=3D"ltr">&lt;<a href=3D"mailto:Dag.Wanvik@sun.com">Dag.Wan=
vik@sun.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" styl=
e=3D"border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; =
padding-left: 1ex;">
<br>
Hi Hiranya,<br>
<div class=3D"im"><br>
Hiranya Jayathilaka &lt;<a href=3D"mailto:hiranya911@gmail.com">hiranya911@=
gmail.com</a>&gt; writes:<br>
<br>
&gt; Hi Folks,<br>
&gt;<br>
&gt; I&#39;m in the middle of writing the new tests for dblook. When going =
through<br>
&gt; the existing dblook tests I realized that they are not junit tests. So=
me of<br>
&gt; the test classes have main methods. So I was wondering how should I or=
ganize<br>
&gt; the new tests. Should they be written as junit tests or should they be=
<br>
&gt; similar to the existing tests?<br>
<br>
<br>
</div>I had forgotten the old dblook tests were not in JUnit :( Converting<=
br>
those adds a not insignificant extra amount of work for you..<br>
<br>
Maybe you could first build the new tests in JUnit, and if you have<br>
time, convert the old test cases at the end of your effort, </blockquote><d=
iv><br>+1. That&#39;s what I had in mind too.<br><br>Thanks,<br>Hiranya<br>=
=A0</div><blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid =
rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
maybe the<br>
old tests will be fully superceded by your tests in any case.<br>
<br>
If you think converting the old tests will definitely be too much work<br>
given the time remaining, augmenting the present tests is also<br>
acceptable, I think. The community could convert them to JUnit<br>
later. I think it is more important that you get new tests in at all,<br>
than what format they are in.<br>
<br>
Obviously, we would prefer JUnit ;-) since we are trying to get rid of<br>
the canon based tests.<br>
<br>
Thanks again for your efforts!<br>
<font color=3D"#888888"><br>
Dag<br>
</font></blockquote></div><br><br>

--0015174c141820276d047163e23d--