July 11, 2016

How Baseline Testing can help with your legacy code bases

Baseline Testing, also known as characterization testing provides multiple benefits to your organization. One of which is filling the gaps on legacy code bases that have inadequate test cases. Often the lack of sufficient tests means that when the application is modified the changes break existing functionality. Having test cases that formalize and hold the behavior of an existing piece of software enables developers to refactor and enhance the application with confidence. Vector Software’s proprietary technology allows the company to build huge suites of test cases for legacy applications, which provide an immediate improvement to quality. 

Automatic test case generation (ATG) is a huge benefit that comes with Vector Software’s technology. We can quickly provide a baseline set... Continue reading »

Posted by Bill McCaffrey in Technical Debt

July 07, 2016

Vector Software’s Dr Andrew V. Jones Presenting at NIST Software Security Workshop

Dr Andrew V. Jones will present “Dynamically Proving That Security Issues Exist” at the National Institute of Standards and Technology’s (NIST) Software Measures and Metrics to Reduce Security Vulnerabilities Workshop on Tuesday, July 12, 2016 at 1:40 PM ET in the Green Auditorium at NIST in Gaithersburg, Maryland.

Dr Jones’ presentation will focus on more accurate ways to perform security testing to find and prove the legitimacy of vulnerabilities, significantly reducing false positive results. 

Posted by Anna Barcelos in Events, Security, Software Quality

July 06, 2016

Actionable Quality Metrics: The Missing Link to Improving Software Quality

Software projects typically fall into two categories: maintenance of legacy applications and development of new applications.  Naturally, each presents its own unique challenge. For example, legacy applications are often under-tested and overly complex, and understanding where to start is the biggest challenge to improving quality. With new development, the challenge is typically release readiness – the task is determining how much work has been done and how much remains to be done. 

Posted by Bill McCaffrey in Software Quality