How to Write Test Cases in Manual Testing?

Dapheny Murphy | January 30, 2023

How to Write Test Cases in Manual Testing?

A test case specifies the inputs, the execution conditions, the testing procedure, and the expected results to describe a single test to be run for a particular software testing objective.

So while writing a test case in manual testing one should be aware of the components that are used to write a test case. Test cases have several components.

When writing a test case one should use the below-mentioned components as much as possible to ensure that a test case is easily understandable.

  1. Title

    The title is the first component of a test case, it should be easy to understand, and the user should be able to understand the test scenario after reading the title.

  2. Prerequisites:

    This includes all the pre-requirements necessary for the test to be carried out.

  3. Test Steps

    The Test Steps are the steps that need to be performed to perform the scenario in a test case.

  4. Expected Result

    Once the test steps have been performed, define the result that should be displayed.

  5. Test Data

    Test Data contains the data that is to be used for testing purposes. Such as:

    • User information
    • Any specific file that is to be uploaded
    • Any specific values that needed to be used for testing

Other Things That Need to Be Remembered While Writing Test Cases in Manual Testing

  1. Test Suite

    A test suite is a set number of test cases, so while writing a test case make sure to create a test case in the correct suite. The suite here signifies the module for which the test case is written, so the test case should always be written in the correct suite.

  2. Priority

    Test case priority helps the user to understand in which order test cases should be executed.

  3. Component

    This test case belongs to which component of the application or a test suite.

  4. Keywords

    You can also add a few keywords to the test cases which can refer to the related defects or any other reference.

  5. Screenshots/Screencasts

    Screenshots and screencasts can be added to the test cases for training purposes or for finding the bugs in regression.


This publication is for informational purposes only, and nothing contained in it should be considered legal advice. We expressly disclaim any warranty or responsibility for damages arising out of this information and encourage you to consult with legal counsel regarding your specific needs. We do not undertake any duty to update previously posted materials.

Post a Comment