Ohloh by Black Duck

 Follow @ Meta   Join Now

Project Summary

  Analyzed 5 days ago based on code collected 5 days ago.

The idea for this project came from real life. We just needed to make sure that all the specification described by the source javadoc is covered with unit tests.

The simplest idea to make sure everything was properly and completely tested was to create a test for each sentence (or couple of related sentences) from the source javadoc. But then how do you make sure everything is covered?

This tool adresses this problem. You annotate each test with a sentence from the javadoc. The tool creates a report showing which parts of the javadoc are covered with tests, and which not.

The project also includes a maven plugin.

THIS PROJECT IS WORK IN PROGRESS and is NOT READY YET :)

Share

Quick Reference

Project Links:

Code Locations:
http://javadoc-test-coverage.goo...
Licenses:
Apache-2.0
Similar Projects:
Managers:
Become the first manager for javadoc-test-coverage
Browse Code

In a Nutshell, javadoc-test-coverage...

Languages

Java 		61%
XML 		39%
DOS batch script 		<1%
 
 

Lines of Code

 

Activity

30 Day Summary Apr 14 2013 — May 14 2013

12 Month Summary May 14 2012 — May 14 2013

Commits per Month

Community

Ratings

Be the first to rate this project
 
Click to add your rating
 
Review this Project!

Most Recent Contributors

Anon32 webkai123 Anon32 wmlynar
Anon32 [anonymous]    

Contributors per Month

 
 
 

Project Summary

Code Data

SCM Data

Community Data

 

Creative Commons License Copyright © 2013 Black Duck Software, Inc. and its contributors, Some Rights Reserved. Unless otherwise marked, this work is licensed under a Creative Commons Attribution 3.0 Unported License . Ohloh ® and the Ohloh logo are trademarks of Black Duck Software, Inc. in the United States and/or other jurisdictions. All other trademarks are the property of their respective holders.