Semantic Designs of Austin Texas announces general availability of the Test Coverage Tool for C# 4.0. The Test Coverage Tool parses C# source code, analyzes it, and generates new code can be compiled and run to determine exactly what lines of code have been executed as part of one or more tests. An easy-to-understand graphic display of code coverage along with overall metrics is the result of the tool. Semantic Designs tools are in use with a variety of critical enterprise and embedded systems applications, with C# just one of a variety of languages supported.
(PRWEB) April 8, 2010 -- Today’s Agile development processes put an emphasis on building and regularly executing tests, but how do you know what has really been tested? Oftentimes tests exercise a small percentage of the overall system code, regardless of how many tests exist or how often they are run. It is highly important to know exactly which lines of code have been tested and the overall percentage of code “covered” is a key metric for Software Quality Assurance.
"Test coverage analysis is critical to effective modern software quality assessment. This tool lets you know where you really stand," says Dr. Ira Baxter, Founder and CEO of Semantic Designs.
The C# (C-Sharp) Test Coverage tool enables the collection and display of code coverage data on C# software source code bases of any size. It is a member of Semantic Design's family of Test Coverage Tools and works in conjunction with Semantic Design’s other tools and support for other languages. Semantic Designs specializes in dealing with very large codes bases in multiple languages. Multi-million line systems are no problem for this line of tools.
Semantic Design's test coverage tools operate by inserting language-specific probes for each basic block in the source files of interest before compilation/execution. At execution time, the probes record which blocks were executed ("coverage data"). On completion of execution, the coverage data is typically written to a test coverage vector file. Finally, the test coverage data is displayed on top of browsable source text for the system under test, enabling a test engineer to see what code has (or has not) been executed, and to see overall statistics on coverage data. Additional tests can then be added to extend code coverage to meet Software Quality Assurance goals.
Read the full story at http://www.prweb.com/releases/2010/04/prweb3829654.htm.
Copyright©2010 Vocus, Inc.
All rights reserved