Mailing-List: contact ooo-qa-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ooo-qa@incubator.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <503933F2.9080308@apache.org>
Date: Sat, 25 Aug 2012 16:22:10 -0400
From: Carl Marcum <cmarcum@apache.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:14.0) Gecko/20120717 Thunderbird/14.0
MIME-Version: 1.0
To: ooo-qa@incubator.apache.org
Subject: unit testing philosophy
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi all,

I'm new to the qa list and joined because I would like to learn more 
about testing and as a java dev, I think this is an area I can 
contribute to the project.

I've been working on updating the netbeans plugin and that's working, 
now I'm looking at the unit and qa-funtional tests.

When I run the tests only about 60% pass. When I start looking at what 
is failing I'm seeing a lot of prototype tests that just setup and call 
fail. example:

     /**
      * Test of locateOffice method, of class IxLocator.
      */
     public void testLocateOffice() {
         System.out.println("locateOffice");
         IxLocator instance = null;
         instance.locateOffice();
         // TODO review the generated test code and remove the default 
call to fail.
         fail("The test case is a prototype.");

Is it better to have:
100% coverage and 50% fail because of prototypes
or
50% coverage and 100% pass (no prototypes or just not call fail)?

Thanks,
Carl