| Projects on Google Code | Results 1 - 10 of 30 |
A code coverage tool for .NET. Forked from PartCover.
#summary Welcome to the Coverage Report homepage
Project Home: http://csharptest.net
----
== Summary ==
This project is for those of you that have been continuing to use the free version of NCover and the reporting tool NCoverExplorer. As you may have encoutered issues with the report gene...
A code coverage tool for JVM based languages.
Features:
* Bytecode based complexity and coverage analysis
* Show line coverage if the source is available
* Project Dashboard
* Apache MavenPlugin
* Apache AntTasks
* Emma compatible XML report generation.
= Plan =
# Data merging....
In applications such as vacuuming, cleaning and demining, a robot must cover an unknown surface. The robot accomplishes coverage of an unknown surface by visiting all reachable surfaces in the environment. The efficiency and completeness of coverage is improved by the construction of a topological m...
Html Reporter for [http://www.bullseye.com BullseyeCoverage] tool.
[http://www.bullseye.com BullseyeCoverage] for C/C++ test coverage measurement is powerful to work with from very limited embedded system to enterprise level application. However, there is lack of enough HTML reporting feature. Bu...
shcov is a gcov-like code coverage tester for bourne shell / bash scripts. It also has a [http://ltp.sourceforge.net/coverage/lcov.php lcov]-like HTML output generator to present coverage results.
http://shcov.googlecode.com/files/shcov-browser.png
The web interface is taken from the [http:/...
This project aims to produce an api to read data from gcno and gcda files. These files are generated when invoking gcc with the -fprofile-arcs and -ftest-coverage options (the same as --coverage in gcc 4.4.x). The motivation for this api was the lack of integrated code coverage tools for eclipse cdt...
This is a simple python script to tie together valgrind and some binutils stuff to get a listing of code that DIDN'T run.
callgrind (in valgrind) has a simple way to find out what code DID run, but I am more interested in what code DIDN'T run since that is the easiest place for bugs to hide.
javascript coverage tool
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 relat...