Quality Assurance

The most compelling QA efficiency derived from code coverage is to maintain a coverage threshold through which all builds sent to QA must satisfy. This will stop careless development efforts and redirect responsibility from the coder reviewing the project to the coder actually creating the project.

Code Coverage Impacts Your Health(care)

Regardless of your political persuasion, I think there are very few developers who don’t cringe when they think about the healthcare.gov debacle that has consumed U.S.and global headlines for the past few months.  System errors, complete outages, screens that wouldn’t load and forms that…   Continue Reading

NCover Collector Merge and Sync Control

NCover Collector and Code Central provide a robust framework for collecting code coverage in testing and quality assurance environments.  These tools make it easier to collect coverage unattended with and provide collection configuration.  Using Code Central as the administrative hub, projects for code collection are…   Continue Reading

Command Line Merge for Code Coverage

.Net code coverage is most meaningful when it gives my team a full view of which portions of our code have been tested. While test runners and ad hoc coverage tools certainly help our developers refine testing and target methods within their .net apps,…   Continue Reading

Coverage Comes to Manual QA

For some time we’ve been increasingly interested in providing coverage data from manual testing back into the development cycle of our software.  Until now it’s been a bit tedious to teach users and even QA engineers to use the old-style NCover 3 command lines…   Continue Reading

Code Central – A New Way To Collaborate

NCover 4 has tipped the scale in favor of testing transparency.  How many of us can unequivocally say we know which lines of code are tested by automated tests and how much that overlaps with manual testing?  Worse yet, where are the gaps?  Most development teams…   Continue Reading