Back To Main Site

A complete guide for writing manual test case with hacks

Nov 13, 2019/Quality Assurance/

“Quality is never an accident; it is always the result of intelligent effort.” – John Ruskin


As the technology is advancing the testing of software has become a norm to tackle the inaccuracy in software. However alone automation testing is not sufficient for many cases, So you will need to do manual testing.


As it is well said, “to be a great software tester you have to have an eye for details".


The test case is written to define “how” and “what”.If the test went well then it will create high value, improve the productivity of the team and help your software testing company to create high-value softwares.In this blog you will get to know about hacks to write manual test cases. Let's begin with reviewing some definitions and parameters for creating test cases.   


Key Takeaways From This Piece Of Article

  • What is a Test Case?

  • What Is Manual Testing?

  • Type Of Manual Testing 

  • Parameter of Manual Test Case 

  • How to create Manual Test Case

  • Tools

  • Hacks


What is a Test Case?

A test case is a starting point of test execution, whereas test case is defined as the set of variables or conditions, expected result, postconditions under which a tester will determine whether a system under test satisfies the requirement or compliance against a specific requirement.

Whereas Wikipedia gives the following definition of a “test case”: A test case in software engineering is a set of conditions under which a tester will determine whether an application, software system or one of its features is working as it was originally established for it to do.


What Is Manual Testing?

Manual testing is the software testing process that is done without the use of automation tools. As all the test cases are executed according to the user perspective by QA tester. It is utilized to ensure that the application is working according to the requirements mentioned in the document.


Manual Testing is the most traditional and fundamental way of testing the process to find the defects of the software. The difference in the expected result and actual result provided by software requirement is defined defect.


Then the defect is fixed by developer and handover to the tester for retesting. After the agile process is complete the user gets bug free software.


There are various methods of manual testing each method is used according to the testing criteria.Type of manual testing is below:


Type Of Manual Testing 


  • Black Box Testing

  • White Box Testing

  • Unit Testing

  • System Testing

  • Integration Testing

  • Acceptance Testing


Parameter of Manual Test Case 


  • Test Case ID: Its Unique Test Case Identification Number.

  • Purpose: Short description of what is being tested

  • Prerequisite: The Compiling condition that must be met before the test case is executed. For example, the user must be logged in.

  • Test Data: The variable and values that is used in test case. Examples: loginID = {Valid loginID, valid email, invalid email, empty} password = {valid, invalid loginID,invalid, empty}

  • Test Steps: Detailed steps for test case execution.

  • Expected Result: The expected result from the test case

  • Actual Results: How the application worked after executing the above testing steps.

  • Result: Does the test “Pass” or “Fail”.

  • Comments: Here tester can add additional important information such as screenshots and descriptions to help the developer with the information they need to correct the defect.


How to create Manual Test Case


Let's take a test case scenario of Login Functionality


Step 1 

A simple test case scenario would be


Step 2

In order to execute the test case, you will need data. Let's add it below



Some time identifying test data can be time-consuming or it may require fresh data. That's why it is necessary to document.


Step 3 


In order to execute test cases, the tester perform a set of activities on AUT (application under test)

As documented below 



Many time step test is not as simple as above, so it needs to be documented carefully


Step 4 

The aim of the test case is to check the behavior of AUT for the expected result.

This need to be documented as below :


During the AUT the tester check the expected result against the actual result to assign Pass or Fail 


Step 5 

The test case includes fields like precondition and postcondition that could be time and date that can be stored in the database.



Tools for manual testing helps in managing and maintaining the Test case. Here are some of the tools that can be used while testing the test case by the tester:  

  • TestLink

TestLink is used for test management.

  • JIRA

This is used as product management tools and it is also used for bug management

  • Mantis

Mantis is used for bug tracking.

  • Postman

Postman is used for API testing.




Testing professionals work hard to test applications and identify defects. And it becomes very frustrating when their viewer rejects the test case. So here are some hacks that will help you in writing the test cases that will help you to improve the quality of software.


  • Keep Simple:- It is unacceptable when the test case is complex as it can't be easily understandable. Test cases are written in simple language and in the software testing company template.

  • Make it reusable:- When you are creating a test case always keep in mind a test can be reused as the same test case can be used in some other test case or its test step can be used.

  • Think about end-user: While writing the test scenario always keep in mind the end-user. If the UX is bad it is bad for the business,so the valued tester is one who understands the end-user and provides a relevant solution to the developer.

  • Stay Organized: The test cases can be managed by organizing, in many companies a spreadsheet is maintained to manage the test cases. As no of test cases increases, it becomes difficult and inefficient for the team to manage. 



In software testing, the manual testing is not the only task to be fulfilled. So you have to plan for the unexpected result and turn it into expected and addressed. 


Read More

Show Less

Add a Comment

Your email address will not be published.