From derby-dev-return-96403-apmail-db-derby-dev-archive=db.apache.org@db.apache.org Mon Jun 11 14:16:01 2012 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 9C0EC98E0 for ; Mon, 11 Jun 2012 14:16:00 +0000 (UTC) Received: (qmail 92831 invoked by uid 500); 11 Jun 2012 14:16:00 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 92756 invoked by uid 500); 11 Jun 2012 14:16:00 -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 92749 invoked by uid 99); 11 Jun 2012 14:16:00 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Jun 2012 14:16:00 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of bpendleton.derby@gmail.com designates 209.85.210.44 as permitted sender) Received: from [209.85.210.44] (HELO mail-pz0-f44.google.com) (209.85.210.44) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Jun 2012 14:15:53 +0000 Received: by dacx6 with SMTP id x6so5442701dac.31 for ; Mon, 11 Jun 2012 07:15:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=aVrtze4WNfpq7b3l4i36GCR3qUpsAzfQHPWf6c2KeZg=; b=fIUSvsIgEiqosktWwdBW7enoYMSf7wPO3nOKC9y1hJQ5g41W57New+AXIPsQEfObco oo4EjWM7InOIDbeNjBUIy96FR/KYcmhN5IDnBDW+FyJ24hhbamoARnpnQLjkYkYos/+G ZQE0fb0Src7GemyPrCmkGBx6kLxAi52ZBg/zxEXl9cp1JiMBZTcW7el9+BYTt7/jRrPQ +3kffCeBxl+Hnrv7Yc/vavCMO4iQ4SvLT4kOWsGA/sStK53DCrdFbnN81lFKAb4MfWBW SQitj6qjASeb2ATYblZgxfGN76QqDJ927u9Fp7RFMeVBYIkKUypCVvVuR0OYDYAuZTIN 3evw== Received: by 10.68.226.65 with SMTP id rq1mr27523499pbc.25.1339424133263; Mon, 11 Jun 2012 07:15:33 -0700 (PDT) Received: from [192.168.0.108] (c-67-170-231-73.hsd1.ca.comcast.net. [67.170.231.73]) by mx.google.com with ESMTPS id qn1sm18621319pbc.9.2012.06.11.07.15.31 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 11 Jun 2012 07:15:32 -0700 (PDT) Message-ID: <4FD5FD81.3050209@gmail.com> Date: Mon, 11 Jun 2012 07:15:29 -0700 From: Bryan Pendleton User-Agent: Mozilla/5.0 (X11; Linux i686; rv:12.0) Gecko/20120430 Thunderbird/12.0.1 MIME-Version: 1.0 To: derby-dev@db.apache.org Subject: Re: Code coverage for client.net package References: <4FBB9DA2.20906@gmail.com> <4FBC26CF.1040500@gmail.com> <4FBC5F02.2010400@gmail.com> <4FC0EDF0.1060303@gmail.com> <4FD3A6A6.8020409@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On 06/11/2012 01:07 AM, Mohamed Nufail wrote: > By analysing those classes, I found that the following methods have no usage at all. This looks like a great collection of methods to focus on. 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? > Also I tried the suggested techniques for coming up with tests, but found it difficult to determine the top-level classes > calling the methods in network client. 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. thanks, bryan