Return-Path: X-Original-To: apmail-db-derby-dev-archive@www.apache.org Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5F19C9F8E for ; Mon, 11 Jun 2012 17:16:26 +0000 (UTC) Received: (qmail 82413 invoked by uid 500); 11 Jun 2012 17:16:26 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 82388 invoked by uid 500); 11 Jun 2012 17:16:26 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 82376 invoked by uid 99); 11 Jun 2012 17:16:25 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Jun 2012 17:16:25 +0000 X-ASF-Spam-Status: No, hits=2.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_REPLY,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of nufail56@gmail.com designates 74.125.82.50 as permitted sender) Received: from [74.125.82.50] (HELO mail-wg0-f50.google.com) (74.125.82.50) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Jun 2012 17:16:19 +0000 Received: by wgbds11 with SMTP id ds11so3467044wgb.31 for ; Mon, 11 Jun 2012 10:15:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=D2ATTSmmpuftbYYDIIv9p3LdnJdoNB9RGNFVYvKsCno=; b=CiixkMwKp+q7Gi2ZaGI26lAXFFpLNCa65cjk6RY4aXXV86/9Bhf/KXVbz582CZRhlL 5Utwl3yt+q6bU9ilhc1ZgMRL82pH98LY6xWF+/QME1nDeKy6iLyMg0zplIHMgJ2jDQOT OPSIS7uLvh98SPIIGHKtX2GTrOmxRbKxgxqFDvKt3xMG4pu6YQl7ewbpQKPohTPDcGw6 JcaXZ9z77ZKqF2m5OWR9ICOfC1ibSzB29UD1SyGW3J8p18ggSf04GKlaVR3eqaHO1rs8 VuYh++MzDUPBT3HjbhC+SJr2suLfW+uO5NaDb9ngQToItzWMrLghzsXWEBBSHrKumX0a lKEA== Received: by 10.180.109.194 with SMTP id hu2mr22437255wib.0.1339434958985; Mon, 11 Jun 2012 10:15:58 -0700 (PDT) MIME-Version: 1.0 Received: by 10.180.5.129 with HTTP; Mon, 11 Jun 2012 10:15:37 -0700 (PDT) In-Reply-To: <4FD5FD81.3050209@gmail.com> References: <4FBB9DA2.20906@gmail.com> <4FBC26CF.1040500@gmail.com> <4FBC5F02.2010400@gmail.com> <4FC0EDF0.1060303@gmail.com> <4FD3A6A6.8020409@gmail.com> <4FD5FD81.3050209@gmail.com> From: Mohamed Nufail Date: Mon, 11 Jun 2012 22:45:37 +0530 Message-ID: Subject: Re: Code coverage for client.net package To: derby-dev@db.apache.org Content-Type: multipart/alternative; boundary=e89a8f3ba8efee181004c235809f --e89a8f3ba8efee181004c235809f Content-Type: text/plain; charset=ISO-8859-1 On Mon, Jun 11, 2012 at 7:45 PM, Bryan Pendleton wrote: > > This looks like a great collection of methods to focus on. > Actually what I meant to say was that these methods are not being called in anywhere. Code inspection from my IDE revealed that these methods are unused. So it might be possible to remove them. > > I suggest that you open a single JIRA, with a subject something like: > > Investigate Network Client methods with zero test coverage > > and list these methods in it. > > Then, as we explore the individual methods one by one, you can open > sub-task JIRA issues as children of the first one, to record the > work that we do for that particular method or methods. > > Do you have a particular method that seems interesting to work on first? > > I don't have a particular idea on which methods would be better to tackle first. But this procedure seems to be the way to go. > > I agree, this is challenging. What debugger or IDE do you use? I think > that most IDEs, including Eclipse, NetBeans, and IntelliJ, have some > tools for finding the callers of a particular method. > > I'm using IntelliJ. But the problem is these methods seem not to be directly called. I'll try running the debugger to see how they work. -- Mohamed Nufail Undergraduate, Department of Computer Science & Engineering, University of Moratuwa. Blog: http://www.nufailm.blogspot.com/ --e89a8f3ba8efee181004c235809f Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Mon, Jun 11, 2012 at 7:45 PM, Bryan P= endleton <bpendleton.derby@gmail.com> wrote:

This looks like a great collection of methods to focus on.
=

Actually what I meant to say was that these methods are not being = called in anywhere. Code inspection from my IDE revealed that these methods= are unused. So it might be possible to remove them.
=A0

I suggest that you open a single JIRA, with a subject something like:

=A0 =A0 =A0 =A0Investigate Network Client methods with zero test coverage<= br>
and list these methods in it.

Then, as we explore the individual methods one by one, you can open
sub-task JIRA issues as children of the first one, to record the
work that we do for that particular method or methods.

Do you have a particular method that seems interesting to work on first?
I don't have a particular id= ea on which methods would be better to tackle first. But this procedure see= ms to be the way to go.
=A0

I agree, this is challenging. What debugger or IDE do you use? I think
that most IDEs, including Eclipse, NetBeans, and IntelliJ, have some
tools for finding the callers of a particular method.


I'm using IntelliJ. But the problem is these met= hods seem not to be directly called. I'll try running the debugger to s= ee how they work.


--
=09 =09 =09 =09

=09 =09 =09 =09

Mohamed Nufail=
Undergraduate,
Department of Computer Science & Engineering,
= University of Moratuwa.
Blog: http:/= /www.nufailm.blogspot.com/


--e89a8f3ba8efee181004c235809f--