Software Quality Assurance & Testing Stack Exchange is a question and answer site for software quality control experts, automation engineers, and software testers. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm using Bullseye code coverage tool. It's great. I'm interested in knowing it's internal functioning. How does it actually work?

share|improve this question
up vote 6 down vote accepted

This is a tool-agnostic question. All of them work the same way: they instrument the code of your system. Each time a line or branch of your code is visited at runtime, the tool caches this information. Afterall, the number of visited lines (or branches) is divided by the total number of lines (or branches). This is done in the scope of a single class/file, package, packages subtrees and whole application.

The code instrumentation can be, however, tool- and language-specific.

Here you will find more info, links and research papers how to implement code coverage tool yourself and how instrumentation in example tools is done.

share|improve this answer
@Abhishek, if you like my answer, don't hesitate to accept it ;-) – dzieciou Apr 10 '13 at 6:10
It is useful to distinguish between tools that instrument the source code, and those that instrument byte code. You pretty much can't get the latter for conventionally compiled languages. – Ira Baxter Jan 27 '14 at 10:17

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.