Workbench Concept in Software Testing

Workbench Concept in Software Testing
October 28 10:00 2011 Print This Article

To understand the technology of software testing it is necessary to understand the workbench concept. A Workbench is a method of documenting how a particular activity must be fulfilled. A workbench is referred to a stages, steps, and assignments.

Workbench Concept in Software Testing

There are five assignments for each workbench:

  1. Input: Each task requires certain input and output parameters. For each workbench we need specific inputs. Input form is the first stage of the workbench.
  2. Perform: The main goal of the workbench is to change the input forms on the expected output ones.
  3. Check: Check ensures that output after the performing achieves the desired result.
  4. Production output: If the check is done correctly the production output becomes the last stage of the workbench.
  5. Rework: If the result after the check doesn’t meet our expectations we need to start again from the step of performance.

In fact, scenarios are not made of one workbench but of many related workbenches. A workbench gives you an opportunity to execute any one task with appropriate software testing.

Let’s discuss the workbench concept:

Requirement phase

The input data – the requirements of clients; we perform a task – writing a document with the customer’s requirements, we check the suitability of a document to all needs of client, and receive the output – requirement document.

Design phase

The input data – the requirement document, we execute the preparing a technical document; review/test is performed to see if the design document is technically right and transfers all the requirements in the requirement document, and receive a technical document.

Execution phase

It is the actual performance of the project. The input data – the technical document; the performance is nothing but realization/ coding according to the technical document, and the output data – the source code.

Testing phase workbench

It is the stage of software testing. The input data – the source code which is required testing; the realization – implementation of the test case and the output – the results of software testing.

Distribution phase

There are two inputs for this step – the source code which requires of customers and the source code with the results of testing. The output of this project is the product which is ready for use.

Maintenance phase

The input – the results of distribution, execution – execution of the last customer requests, the running regression software testing after every changed customer request, and the output is a new release.

Related Posts:

  • No Related Posts

About Article Author

view more articles
Nataliia Vasylyna

View More Articles