Software Testing and Quality Trends to Watch , January 2012

Read Wayne Ariola's predictions re: switching costs, safety-critical compliance, and market-ready software.

4 Software Quality Predictions for 2012 , January 2012

Read Arthur Hicken's predictions re: SQL injection, cloud quality, component testing, Kindle Fire caching testing.

Input Validation: Immunity Against Web Attacks , September 2011

Explains how to prevent injection attacks by using input validation and static analysis to build security into your application.

Code Coverage Awareness , September 2011

Introduces steps for improving code coverage awareness: tools for measuring coverage; understanding the type of coverage provided; identifying and covering uncovered cases.

Code Coverage Density and Test Overlap , September 2011

Explains why test overlap is generally undesirable, introduces test overlap and the imperfection of coverage models, and explores how to achieve properly distributed test density.

Towards Full Regression Test Coverage , September 2011

Explains how to achieve full regression coverage (complete entry/exit coverage) and why complete path coverage is not sufficient.

The Problem with Path Code Coverage , August 2011

Discusses why so few available code coverage analysis tools support path coverage: high number of paths, difficulty identifying and covering paths, representation challenges.

Test Code Coverage Metrics , August 2011

Explores code coverage metrics including statement coverage (block coverage), branch coverage, and path coverage.

Code Coverage Granularity , August 2011

Explains what coverage granularity means, why line-based coverage is meaningless yet popular, and granularity levels for test coverage (line, statements/expression, bytecode instruction).

Dispelling Common Code Coverage Myths and Dodging Pitfalls , August 2011

Introduces common pitfalls and misconceptions regarding code coverage granularity, coverage criteria, coverage density, and test overlap, then it explains what you need to know to choose the best coverage metric for your goals.

Requirements Traceability and Requirements-Based Testing , August 2011

Explores how to achieve requirements traceability, which has become a "must have" capability for teams who need to comply with safety-critical standards such as DO-178B, FDA, IEC 62304, IEC 61508, ISO/DIS 26262, etc.

What Do Developers Hate Most About Static Analysis? , July 2011

Presents results from a recent survey on what developers hate most about static analysis.

Unit Testing: How We Eased the Burden of Our Regression Test Process , May 2011

When Parasoft started with unit testing, our regression test failures weren’t being addressed promptly as the application evolved. This post describes what our team learned.

Increase Unit Testing ROI: Keep Unit Tests in Synch with Your App , May 2011

Establishing a supporting unit test maintenance process and an infrastructure to drive this process and keep it on track is essential for getting a good return on investment from your unit testing efforts.

Unit Testing: Is More Coverage Better? , April 2011

Argues that greater unit testing code coverage is not always better. Also discusses what you can learn by reviewing unit test code coverage.

Unit Testing: Is it Nearing Extinction? , April 2011

Introduces a new approach to unit testing that is designed for functional testing of cloud, RIA, SOA, and other complex applications.

How Can Test-Driven Development (TDD) Be Automated? , January 2011

Explores how automation can make Test-Driven Development (TDD) less painful and more valuable.

Static Code Analysis Rule Set Optimization Can Uncover More Defects , December 2010

Shows how static analysis--specifically, fine-tuning a team's static code analysis rule set--helped Parasoft's development team eliminate defects.

New SD Times Articles on Software Development Management , December 2010

Introduces 2 SD Times articles: one on how to increase software development management and one about the Parasoft Concerto ALM platform.

Static Analysis Finds Software Defects that Functional Tests Miss , December 2010

Provides an example of how static analysis exposes software defects that functional testing would miss.

Parasoft SDLC Productivity Audit , November 2010

An independent audit found that Parasoft's agile development team, using Parasoft's application lifecycle management solution (Concerto), is 8-15X more productive than the industry average.

Software Development Management: Optimizing Project Task Management , November 2010

How software development project task management improves development and QA productivity.

Code Review and Requirements Review: Automating Human Review Tasks , November 2010

How to automate human review processes such as peer code review and requirements review to increase software development productivity and defect prevention.

Software Development Management: Meeting Expectations , November 2010

How software development teams can satisfy management’s expectation about what defines a completed requirement.

Achieving Software Development Productivity Naturally , October 2010

Explains how to to achieve greater levels of developer productivity with a natural software development management process.

Software Development Process Improvement: The Time is Now , October 2010

Why and how to optimize the software development processes to improve quality and efficiency—even while rapidly evolving applications in response to constantly-changing business needs.

Static Analysis and Run Time Error Detection on 64-Bit Platforms , October 2010

Introduces a strategy for identifying run time memory errors and other defects after porting software code to 64-bit processors or platforms.

Static Analysis for Porting Code to 64-Bit Platforms , October 2010

Introduces static analysis rules that help you remove memory errors and other defects when porting code to 64-bit platforms

Porting to 64-Bit Platforms: Why Is it So Challenging? , September 2010

Introduces the potential problems that could occur when you port applications to 64-bit processors.

Memory Error Detection When Porting to 64-Bit Platforms: Preparing for Porting , September 0201

Introduces a process to prepare the application for the porting process: 1. Perform mutation testing via runtime memory error detection; 2. Use static analysis to identify error-prone and non-portable code; 3. Repeat runtime memory error detection; 4. Perform unit testing (Optional)