Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: pass (athena.apache.org: domain of pjj.ccce@gmail.com designates
 209.85.198.190 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=rHah0gO4mfAxkZtEIPReE8QnUb0RwHRURzG0NSDA/Dd0AeNA26BmMY4KeUFcgy5uxJRULS12s/U/hGZdL5Awo5HQFcPtY8dK6oAHgUmLWLXT52QJlxJv4G4FlEA+clnYqWt4lSKN+7bv5BvO3yuy+OkOGezDQllJ8NYb7T44cz8=
Message-ID: <f89074310803230706l34fb9dmb68a5dfb9b41bcd1@mail.gmail.com>
Date: Sun, 23 Mar 2008 22:06:39 +0800
From: "Junjie Peng" <pjj.ccce@gmail.com>
To: derby-dev@db.apache.org
Subject: Re: please tell me emails of the two mentors for GSOC
In-Reply-To: <47E65A46.7050308@sbcglobal.net>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_6996_16429266.1206281199099"
References: <f89074310803220916i4dc81132h3efcc66eb146f74d@mail.gmail.com>
	 <47E65A46.7050308@sbcglobal.net>

------=_Part_6996_16429266.1206281199099
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

   Oh, I got it! Thank you, Kathy! Nice to hear from you! I enjoy unit
testing in my development. It's a good way to look inside a project, and
take knowledge of the framework.
   Below are questions about GSOC:
   1. The task "Convert Derby tests to JUnit and fix Derby bugs " comprises
two parts, what are the weight for each of them?  Does it mean that
converting is just a lightweight task, so should be complemented by the
second task?
   2. Weather the converting task only contains "converting old tests to
JUnit "in the page http://wiki.apache.org/db-derby/DerbyTesting ?
   3.  What should I do is just converting or including writing some new
test case?
   4. I've seen some coverage report about Derby test. Is there some
automatic tool to do this? Or should we develop one?
   5. As for bug-fixing, I feel a puzzle. It seems hard to choose some bugs
to fix for a stranger, I'm not sure about which are suitable for me and the
workload of fixing the bugs. Must I choose the bugs before I apply?

------=_Part_6996_16429266.1206281199099
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<div>
<p>&nbsp;&nbsp; Oh, I got it! Thank you, Kathy! Nice to hear from you! I enjoy unit testing in my development. It&#39;s a good way to look inside a project, and take knowledge of the framework.<br>&nbsp;&nbsp; Below are questions about GSOC:<br>
&nbsp;&nbsp; 1. The task &quot;Convert Derby tests to JUnit and fix Derby bugs &quot; comprises two parts, what are the weight for each of them?&nbsp; Does it mean that converting is just a lightweight task, so should be complemented by the second task?<br>
&nbsp;&nbsp; 2. Weather the converting task only contains "converting old tests to JUnit "in the page <a href="http://wiki.apache.org/db-derby/DerbyTesting">http://wiki.apache.org/db-derby/DerbyTesting</a> ? <br>&nbsp;&nbsp; 3.&nbsp; What should I do is just converting or including writing some new test case?<br>
&nbsp;&nbsp; 4. I've seen some coverage report about Derby test. Is there some automatic tool to do this? Or should we develop one?<br>&nbsp;&nbsp; 5. As for bug-fixing, I feel a puzzle. It seems hard to choose some bugs to fix for a stranger, I&#39;m not sure about which are suitable for me and the workload of fixing the bugs. Must I choose the bugs before I apply? </p>

<p>&nbsp;</p></div>

------=_Part_6996_16429266.1206281199099--