Software Test Design

This is the Second Phase of STLC – Software Testing Life Cycle. The Process of Writing the Test Cases for the Project is known as Software Test Design. Test Engineer is responsible for writing the Test Cases.

  • Every company will be having a Test Case template to write the Test Cases.

Test Case Template:

Test Case Design Template of Software Test Design

 

Modules:

Requirements will be distributed in Modules. These Modules will be available in AUT (Application Under Test).

 

Test Case ID:

The serial no. of the Test Cases will be mentioned here.

 

Test Types:

The Types of Test Cases are below:

  • GUI
  • Validation
  • Positive (+ve)
  • Negative (-ve)
  • DB (Data Base)

 

GUI:

Graphical User Interface (GUI) is related to Design verification like Check Spellings, Alignment, Color, Fonts, Font Styles, Color, Size, Design of the Page etc.

Validation:

Check whether the application is displaying all the expected fields or not.

Positive (+ve):

This is Positive Functional Test Cases, Testing the application will all the valid Test Data.

Negative (-ve):

This is Negative Functional Test Cases, Testing the application will all the invalid Test Data.

Data Base Test Cases:

Test whether the data is properly inserted, available, delete, update, select in the Data Base or not.

 

Priority:

It describes how important the Test Case is to be Pass.

  • There are Four types of Priority given below, based on the importance of the Test Cases:
  • P1, P2, P3, P4

 

P1:

If the Test Case is describing the main functionality then the Priority of Test case will be P1. It means I the P1 Test Case fails, we can’t continue the Testing Further.

P2:

If the Test Case is describing the field level functionality then the Priority will be P2. It means if P2 Test Case fails, we can continue the Testing but it is needed to be Pass.

P3:

All GUI Test Cases Priority will be P3.

P4:

Test Engineer is having the option to give the Suggestions, so the Priority of the Suggestions will be P4.

 

Test Scenario:

Test Scenario means a flow which we are using for Testing. The requirement will be divided into multiple flows (Scenarios) & Testing will be performed in all the possible scenarios.

 

Pre – Condition:

The Condition which is required to execute the Test Scenario with steps.

 

Test Steps:

The detailed steps to execute the Test Scenarios will be described here. Based on the Test Steps, the Test Engineer will execute the Test Cases.

 

Expected Result:

Most of the Time while writing the Test Cases, the Test Engineer will not be having the application with him, so he/she will assume the result for the Scenarios. That will be described under Expected Result field.

 

Actual Result:

Once the build is released to the Testing Team, So the Testers will execute the Test Cases while executing the Test Cases the Tester will observe the actual behavior of the application and it will be updated under Actual Result field.

 

Result:

While executing the Test Cases, the Test Engineer will compare the Actual Result with the Expected Result, if both results matching then Test Engineer will give the Result as Pass and if both are not matching then he/she will give the Result as Fail.

 

Click here for STLC – Software Testing Life Cycle

Click here for Software Testing Plan

One Thought on Software Test Design

  1. Software Test Design is Very Useful and impressive article.
    Thank you, soo much for sharing this article.
    I also want some examples on test case template wherefrom it will be more clear to the user.

Leave a Comment