About the Book
Please note that the content of this book primarily consists of articles available from Wikipedia or other free sources online. Pages: 33. Chapters: Code coverage, Parasoft, FitNesse, TPT, Valgrind, Codenomicon, Instruction set simulator, JSystem, TestComplete, IBM OLIVER, QuickCheck, MALPAS Software Static Analysis Toolset, Doctest, Phantom automation language, SIMMON, Frama-C, Enterprise test software, SemmleCode, Atlassian IDE Connector, Itko, Parasoft Concerto, DejaGnu, Automation Anywhere, Soatest, QF-Test, Mu Dynamics, Jtest, TestArchitect, Replay Solutions, WebUI Test Studio, LDRA Testbed, HTTP Test Tool, Reductio, Framework for Integrated Test, SIMON, Sahi, Duma, DevPartner, Clover, DOM Inspector, Electric Fence, WebScarab, Averna test engineering, Testwell CTC++, Litmus, RIATest, RSpec, VB Watch, Debug new, Fault Simulator, RAISE, ECATT, Introspector, CAST tool. Excerpt: Code coverage is a measure used in software testing. It describes the degree to which the source code of a program has been tested. It is a form of testing that inspects the code directly and is therefore a form of white box testing. Code coverage was among the first methods invented for systematic software testing. The first published reference was by Miller and Maloney in Communications of the ACM in 1963. Code coverage is one consideration in the safety certification of avionics equipment. The standard by which avionics gear is certified by the Federal Aviation Administration (FAA) is documented in DO-178B. To measure how well the program is exercised by a test suite, one or more coverage criteria are used. There are a number of coverage criteria, the main ones being: For example, consider the following C++ function: Assume this function is a part of some bigger program and this program was run with some test suite. In languages, like Pascal, where standard boolean operations are not short circuited, condition coverage does not necessarily imply decision coverage. For example, consid...
