Model-Driven Test Design

Model-Driven Test Design

We define test design to be the method of making input values that will effectively test software. this is often the foremost mathematical and the technically challenging part of testing, however, academics can easily forget that this is often only a little a part of testing. The job of developing tests is often divided into four discrete tasks: test design, test automation, test execution, and test evaluation. Many organizations assign an equivalent person to all or any tasks. However, each task requires different skills, background, education, and training. Assigning an equivalent person to all or any of these tasks is like assigning an equivalent software developer to requirements, design, implementation, integration, and configuration control. Although this was common in previous decades, few companies today assign an equivalent engineer to all or any development tasks.

Engineers specialize, sometimes temporarily, sometimes for a project, and sometimes for his or her entire career. But should test organizations still assign the same people to all or any test tasks? They require different skills, and it is unreasonable to expect all testers to be good in the least tasks, so this clearly wastes resources. the subsequent subsections analyze each of those tasks in detail.

  1. Test Design
  2. Test Automation
  3. Test Execution
  4. Test Evaluation
  5. Test Personnel and Abstraction

%d bloggers like this: