
	Where results make sense

Topic: Code coverage

Related Topics

Software testing

Automated testing

Black box testing

Static code analysis

Open source

Extreme Programming

Software engineering

Quality assurance

Jackson Structured Programming

Rational Unified Process

Structured programming

List of software engineering topics

CMM

Software development process

Cleanroom

	Testing and Code Coverage
		Using code coverage is a way to try to cover more of the testing problem space so that we come closer to proving the absence of faults, or at least the absence of a certain class of faults.
		Code coverage is a white box testing methodology, that is it requires knowledge of and access to the code itself rather than simply using the interface provided.
		Code coverage is probably most useful during the module testing phase, though it also has benefit during integration testing and probably at other times, depending on how and what you are testing.
	homepage.hispeed.ch /pjcj/testing_and_code_coverage/paper.html (4310 words)

	Code Coverage
		Code coverage measurement simply determines those statements in a body of code have been executed through a test run and those which have not.
		Code coverage is part of a feedback loop in the development process.
		As tests are developed, code coverage highlights aspects of the code which may not be adequately tested and which require additional testing.
	www.cenqua.com /clover/doc/coverage/intro.html (717 words)

	JavaRanch Journal - January 2004 - Introduction to Code Coverage
		Code coverage can be classified as white-box testing or structural testing because the "assertions" are made against the internals of our classes, not against the system's interfaces or contracts.
		Code coverage analysis could be implemented by having the virtual machine keep count of which parts of the loaded classes are executed.
		In practice, source code linking means that, as a part of the code coverage report, the tool has generated annotated copies of the actual source code, highlighting the parts which are not covered by your tests.
	www.javaranch.com /newsletter/200401/IntroToCodeCoverage.html (3618 words)

	Code Coverage Analysis
		Basic block coverage is the same as statement coverage except the unit of code measured is each sequence of non-branching statements.
		One argument in favor of statement coverage over other measures is that faults are evenly distributed through code; therefore the percentage of executable statements covered reflects the percentage of faults discovered.
		Condition/Decision Coverage is a hybrid measure composed by the union of condition coverage and decision coverage.
	www.bullseye.com /coverage.html (3138 words)

	Advocating the use of code coverage
		The use of a code coverage tool is usually combined with the use of some kind of automated test suite.
		Code coverage can only tell you how much of your code is being tested.
		My code coverage is 100%, but the truth is that this particular method might be robust, or it might not.
	software.ericsink.com /articles/Code_Coverage.html (2222 words)

	Code coverage - Wikipedia, the free encyclopedia
		Code coverage techniques were amongst the first techniques invented for systematic software testing.
		Techniques for practical path coverage testing instead attempt to identify classes of code paths that differ only in the number of loop executions, and to achieve "basis path" coverage the tester must cover all the path classes.
		Code coverage is ultimately expressed as a percentage, as in "We have tested 67% of the code." The meaning of this depends on what form(s) of code coverage have been used, as 67% path coverage is more comprehensive than 67% statement coverage.
	en.wikipedia.org /wiki/Code_coverage (598 words)

	Classworking toolkit: Cover your code with Hansel and Gretel
		Code coverage tools let you expand the unit testing mantra of "clean and green" to "clean, green, and covered," with real benefits to the effectiveness of your unit tests.
		Adding instrumentation to your code slows execution slightly, and if you run a large set of tests for your application, the performance loss due to instrumentation may be a serious concern (especially if you have tests that are timing-sensitive).
		Coverage tests let you see which code is actually being executed in a class or application.
	www.ibm.com /developerworks/library/j-cwt02095/index.html?ca=drs-j0805 (3177 words)

	Code Coverage - Mono (Site not responding. Last check: 2007-09-09)
		Code Coverage can be used to track how many of the code paths that your program is using are actually exercised.
		MonoCov is made up of two components: a code coverage module, and a GUI interface for doing code coverage.
		By default code coverage will default to all the assemblies loaded, you can limit this by specifying the assembly name, for example to perform code coverage in the routines of your program use, for example the following command line limits the code coverage to routines in the "demo" assembly:
	www.mono-project.com /Code_Coverage (379 words)

	Kaner: Software Negligence & Testing Coverage
		This "completeness" is measured only relative to a specific population of possible test cases, such as lines of code, branches, n-length sub-paths, predicates, etc. Even if you achieve complete coverage for a given population of tests (such as, all lines of code tested), you have not done complete, or even adequate, testing.
		Most traditional coverage measures look at the simplest building blocks of the program (lines of code) and the flow of control from one line to the next.
		For example, 100% line coverage doesn't just mean that you've executed every line of code; it also means that you've tested for every bug that can be revealed by simple execution of a line of code.
	www.kaner.com /coverage.htm (7299 words)

	EMMA: a free Java code coverage tool
		EMMA is an open-source toolkit for measuring and reporting Java code coverage.
		Coverage stats are aggregated at method, class, package, and "all classes" levels.
		Coverage data obtained in different instrumentation or test runs can be merged together.
	emma.sourceforge.net (419 words)

	Tony Obermeit on Code Coverage Lessons
		Code coverage is a metric that tells you how much of the source code for an application is run when the unit tests for the application are run.
		The code coverage tools provide a progress bar which is green for 100% and red for anything less.
		The conclusion was that 100% coverage was the answer because moving away from 100% to anything less is a slippery slope and once you start down that slope it is very difficult to recover.
	homepage.mac.com /hey.you/lessons.html (3436 words)

	How to: Obtain Code Coverage Data
		Code coverage data is gathered when artifacts, typically binary files, have been instrumented and, during a test run, are loaded into memory.
		Code coverage data cannot be collected for an application that is running in a 64-bit process.
		Therefore, when you have requested code coverage data while testing such an application, the test engine sets the “32BIT” flag in the Portable Executable (PE) header of the assembly to be instrumented.
	msdn2.microsoft.com /en-us/library/ms182496(VS.80).aspx (1168 words)

	Devel::Cover - Code coverage metrics for Perl
		Code coverage can be considered as an indirect measure of quality.
		Code coverage data are collected using a pluggable runops function which counts how many times each op is executed.
		Coverage data for path coverage are not yet collected.
	cpan.uwinnipeg.ca /htdocs/Devel-Cover/Devel/Cover.html (1013 words)

	eigenclass - rcov: code coverage for Ruby
		Code coverage shouldn't be abused (in few words, C0 coverage guarantees nothing) but it's still useful for testing: it will at least tell you when your tests need more work, and most importantly where.
		C0 coverage analysis (as done by rcov) tells you which lines of code have been executed: you typically use it to find the areas of your program that have not been sufficiently tested, i.e.
		As for C2 coverage, it's usually not possible to make it very high: you can keep it as an indirect measure of quality, but the gain/cost ratio is lower than for C0-1 coverage, I guess.
	eigenclass.org /hiki.rb?rcov (1093 words)

	A Buyer's Guide to Code Coverage Terminology
		Discussions of coverage can get hung up on name debates, with endless claims about what the right name is and what, precisely, different names mean.
		A line coverage tool could then tell me which of these lines of code had never been reached by the execution of any of my tests.
		A line coverage tool could only tell you that you'd executed post_loop_cleanup(), not whether you got there because you fell out of the loop or because the internal break statement "broke out of the loop".
	www.testing.com /writings/coverage-terminology.html (1604 words)

	Ned Batchelder: coverage
		Coverage.py is a Python module that measures code coverage during Python execution.
		It uses the code analysis tools and tracing hooks provided in the Python standard library to determine which lines are executable, and which have been executed.
		This is useful if you have lines of code that you know will not be executed, and you don't want the coverage report to be filled with their noise.
	www.nedbatchelder.com /code/modules/coverage.html (2385 words)

	SureCov - Code Coverage
		Color-coded bubble diagrams and source code clearly show which sections of the design remain to be adequately covered.
		Code that has been executed but not from all possible combinations is yellow.
		By analyzing the source code without burdening the simulator, typical overhead is 3x less than other coverage tools.
	www.verisity.com /products/surecov.html (494 words)

	DGR's NM ZIP Code Coverage
		This ZIP Code coverage is based primarily on the U.S. Postal Service ZIP Code boundaries as they are depicted by Geographic Data Technology's (GDT's) Dynamap digital database.
		Please note that the ZIP Code coverage (although modified by DGR) is still subject to license regulations by Geographic Data Technology (GDT).
		Ten of the polygons are duplicates (due to ZIP Codes that crossed county boundaries and are counted more than once), one is the universal polygon present in all ARC/INFO generated coverages, and two seemed to be Texas ZIP Codes that were misassigned to New Mexico.
	www.unm.edu /~dgrint/gravzip.html (831 words)

	Koalog Code Coverage
		Hence, the code coverage computation becomes a simple task that can be easily integrated into a more global procedure for code quality insurance.
		Session merging is particularly interesting when one wants to compute an overall code coverage result for distinct executions of the same application: executions with different parameters, executions of different scenarii.
		The only difference between the evaluation version and the commercial version is that the former limits the code coverage computation to 100 classes and can only be used for a period of 15 days.
	www.koalog.com /php/kover.php (449 words)

	TestDriven.NET by Jamie Cansdale : Code Coverage Tips (Site not responding. Last check: 2007-09-09)
		To merge the code coverage results from multiple test projects, you need to select all of the test projects you want to execute.
		Coverage' and all of the test run results will be merged.
		By default the coverage test runner will use Team Coverage if a Team version of Visual Studio 2005 is being used.
	weblogs.asp.net /nunitaddin/archive/2006/06/20/Code-Coverage-Tips.aspx (331 words)

	NCover - Code Coverage for .NET
		NCover provides statistics about your code, telling you how many times each line of code was executed during a particular run of the application.
		The most common use of code coverage analysis is to provide a measurement of how thoroughly your unit tests exercise your code.
		Code coverage measurement is a vital part of a healthy build environment.
	www.ncover.org (415 words)

	Code Coverage
		I could have spent that time refactoring my code so that it is clean, talking to the customer so I understand the problem, and talking to the other programmers so I understand the system.
		A technique such as code coverage must have a very high payoff indeed to be more worthwhile.
		I won't claim that every line of code I write is like that (don't I wish!), but it turns out to be pretty easy to make tests that adequately exercise all the branches when there aren't that many branches to begin with.
	c2.com /cgi/wiki?CodeCoverage (875 words)

	Passing the Test: Magellan Improves Your Code
		The Magellan Code Coverage Framework, developed by the Test Effectiveness group in the Programmer Productivity Research Center (PPRC), provides Microsoft testers with empirical data that helps answer some basic questions.
		A primary goal of the Magellan team has been to provide a solution that can be employed by a small team with a single binary, on up to the Windows team, who are responsible for thousands of binaries and millions of test cases.
		The Scout test prioritization tool in Magellan analyzes the code coverage information in a Magellan database and projects the coverage of those tests onto new versions of the program files.
	research.microsoft.com /displayArticle.aspx?id=707 (855 words)

	Cenqua Clover Code Coverage for Java
		It discovers sections of code that are not being adequately exercised by your unit tests.
		Coverage reports can be published in HTML or PDF and shared with the development team or project management.
		Clover can also be used to find "dead code" in an application; code that is no longer used by the application that can be safely removed.
	www.cenqua.com /clover (431 words)

	Open Source Code Coverage Tools in Java
		This gets code coverage where it belongs: helping with design and implementation before the code is checked in.
		It generates a report from your code to graphically show you how many of your project's methods are being tested, and how well.
		After instrumenting your code and running your tests, a report is generated allowing you to view information coverage figures from a project level right down to the individual line of code.
	java-source.net /open-source/code-coverage (644 words)

	Xpediter/Code Coverage - Validate Testing Thoroughness and Provide Application Analysis
		The ability to target and focus development and testing efforts where they are needed can mean the difference between meeting a deadline and missing it.
		Xpediter/Code Coverage is instrumental in both the analysis and testing phase of application development.
		In the testing phase, Xpediter/Code Coverage specifically reports which lines of code have or have not been executed, and, correspondingly, what percentage of a mainframe application has or has not been tested.
	www.compuware.com /products/xpediter/2002_ENG_HTML.htm (315 words)

	Files: Code Coverage.wmv
		Code Coverage (2:19) After running unit tests against your code, you may want to determine how complete your unit tests are and what code has not been tested by the current collection of tests.
		VSTS Code Coverage provides both a visual tool as well as tabular metrics on the effectiveness of your unit tests.
		This video demonstrates how to enable and interpret code coverage data.
	teamsystemrocks.com /files/10/vste-dev/entry191.aspx (73 words)

	Bullseye Testing Technology
		Due to power failure and infrastructure damage caused by a powerful wind storm, we are operating a minimal work load until approximately 1 Jan 2007.
		BullseyeCoverage is the leading C++ code coverage analyzer in usability, reliability, and platform support.
		Quickly find untested C++ code and measure testing completeness.
	www.bullseye.com (56 words)

	GroboUtils - Welcome
		The CodeCoverage package contains a tool to help you discover what parts of your code have not executed during unit tests.
		There are several commercially available code coverage tools for Java, but they all require a large fee to use.
		This is a 100% Pure Java implementation of a Code Coverage tool.
	groboutils.sourceforge.net /codecoverage (124 words)

	SourceForge.net: EMMA code coverage
		EMMA is a fast Java code coverage tool based on bytecode instrumentation.
		It differs from the existing tools by enabling coverage profiling on large scale enterprise software projects with simultaneous emphasis on fast individual development.
		unitcover: a NetBeans code coverage plugin based on EMMA
	sourceforge.net /projects/emma (125 words)

Try your search on: Qwika (all wikis)