Attached is a report showing the current starte of nmaven junit test code coverage. Here are some of the important metrics.
Class Coverage (35 / 95) - 37% Method Coverage (168/595) - 28% Block Coverage (2719/16346) - 17% Line Coverage (646.4/3589) - 18% The important thing to note is that this report only includes the components that have unit tests, which is a total of 8 projects. If all components were considered, those numbers would be a fraction of their current value. Does anyone know of any documentation as to best practices for unit testing maven plugins? It seems to be an inherently difficult task and I imagine it would require complex sets of mock objects. Any advice or examples in this area would be appreciated. Thanks, Evan On 5/25/07, Evan Worley <[EMAIL PROTECTED]> wrote:
Sure, sounds good. I just got setup on the trunk and I will do some initial code coverage analysis to see how much we can improve. I will start working unit testing from the java side next week. -Evan On 5/24/07, Shane Isbell <[EMAIL PROTECTED]> wrote: > > Thanks Evan. Personally, I am most uncomfortable with the existing unit > test > coverage for both .NET and Java (4). I wrote a number of unit tests for > the > dotnet-vendor module (since that had the highest defect rate) but the > next > most critical module dotnet-executable is sitting at zero unit tests. > Also > the NMaven.Plugin module (.NET) is a critical component with no unit > test > coverage. So either of those would be a good candidate to start with. > > If you work on any NUnit tests, you can run the fxcop (see getting > started > section of website) to do code-analysis before-hand. > > Thanks Again, > Shane > > > On 5/24/07, Evan Worley < [EMAIL PROTECTED]> wrote: > > > > Shane, > > > > I am not surprised you feel overwhelmed, you do an amazing amount of > work > > on > > this. > > > > I can help with 1, 2, and 4. Which is the highest priority? > > > > -Evan > > > > On 5/24/07, Shane Isbell <[EMAIL PROTECTED]> wrote: > > > > > > I feel overwhelmed with all that needs to get done with the NMaven > IDE > > and > > > know that I am neglecting a lot of important details, particularly > in > > > regards to code quality and testing; these details are going to keep > > > mounting up on top of each other. We have Néstor helping out with > the > > > Linux > > > testing, which is a good start. Could I get a list of people who > would > > be > > > interested in helping out with any of the following? > > > > > > 1) Helping to prepare for a release (starting with getting the > license > > > info > > > into all of the file headers) > > > 2) FxCop pointed out a whole list of suggestions for fixing the .NET > > code, > > > so I need someone to look that over > > > 3) The half-completed NCover and Sandcastle plugins need work. > > > 4) The unit test coverage for both NUnit and JUnit is still poor ( > doubt > > > that we have more than 5% code coverage, 0% on the .NET side). > > > 5) Find out how to use log4net ( http://logging.apache.org/log4net/) > with > > > NMaven. Log4net is a top level project and we should be using it. > This > > > work > > > would involve: 1) replacing Console statements with log4net > > statements'2) > > > importing of log4net libs during build; 3) dumping the existing > NMaven > > > logging component (based on java.util.logging) that handles the > logging > > > for > > > both VS and SD > > > 6) Get NMaven working with log4net and/or Lucene.NET. We can provide > the > > > patches to mavenize those projects and work through any issues that > may > > > have. > > > > > > Regards, > > > Shane > > > > > >
