By Darryl Koivisto and Deepak Shankar, Mirabilis DesignEmbedded.com (07/20/09, 07:54:00 PM EDT)
Coming up with a Test Plan is the hardest job in a product company. Engineers like to develop cool products; marketing likes to tout the list of features; and QA/Test lingers in the background with little investment and a very tiny place in the schedule. Productivity is only as great as the quality of your product.
This article discusses our experience at Mirabilis Design in developing a comprehensive test and support plan. The complexity of the software required that we split the testing into sections- Graphical User Interface, feature library, Documentation, Web Links, Simulator or analytics and Database. This allowed some of the tests to be be fully automated while others require visual inspections.
The purpose of the test plan is to maximize the product quality, test the largest number of operating scenarios, ensure that models are upward compatible and identify incorrect operations.
In addition, the Test Plan is designed to address several unique features. In the case of our software these were mixed domains simulation and hierarchical considerations for memory, virtual connection, and virtual machine operations. In our discussion of the plan we came up with we will describe these aspects of software testing:
- Background, Scope, Defects and Failures, Compatibility, Input Combinations and Preconditions, Static vs. Dynamic Testing, Software Verification and Validation, Software Testing Team, Software Quality Assurance (SQA)
- Concept of Baseline Functionality
- Baseline Libraries
- New Libraries Based on Baseline Functionality
- Regression Testing
- Other Specific Block Issues to be Addressed
Click here to read more ...