Create a Manual Test Case in SimplifyQA

A manual test case is a set of instructions that a tester follows to verify a specific functionality of a software application.It outlines the steps to be performed, the expected results, and the actual results obtained during testing.

In this section we will guide you through the process of creating manual test cases within our test case management tool.

Prerequisites:

  • A clear understanding of the software feature or functionality you're testing.

  • Access to the project in which you want to work in SimplifyQA.

Purpose of Manual Testing

  • Uncovers defects: Manual testing can identify issues that automation might miss, especially those related to user experience.

  • Exploratory testing: Testers can deviate from the script to explore different scenarios and find unexpected issues.

  • Usability testing: Manual testing helps evaluate the software's user-friendliness.

  • Initial testing: Manual testing is often used as a starting point before automation is implemented.

How to create Manual Test Case?

Now let's learn how to work with manual test case in SimplifyQA. There are two approaches to creating manual test cases.

Approach 1 : Generate Manual Test Case from User Story

  1. Open the User Story

    • Navigate to the User Stories section.

    • Select the desired user story from which you want to generate test cases.

  2. Generate Manual Test Case

    • Click on the Generate Manual Test Case button.

    • The system will automatically create manual test cases based on the details of the user story.

    • Both positive and negative scenarios are included in the generated test cases.

  3. Select Required Test Cases

    • A list of generated test cases will be displayed.

    • Each test case will have a checkbox next to it.

    • Review the list and select only the test cases you want to keep by checking the boxes.

  4. View in Test Case Section

    • Once selected, the newly created manual test cases will automatically appear in the Test Case section.

    • You can further edit, execute, or manage them as per your testing needs.

Approach 2 : Generate Manual Test Case

1. Navigate to Test Case

To create a new test case in SimplifyQA, open your desired project and navigate to test case section from the left menu.

2. Create a Test Case

Locate the '+ Test Case' button and choose 'Manual' and select the desired platform for which you are creating a manual test case.

3. Create Test Steps

  • For each step, provide:

    • Detailed step description (e.g., "Navigate to the e-commerce website and browse the product catalog.")

    • Expected result (e.g., "Website loads correctly, product catalog is visible and functional.")

    • Parameters: Add Parameters required for the step. Understand parameters in details here.

  • Test Data: Provide the data for the parameters added. Learn how to manage data for a test case here Data Driven Testing in SimplifyQA.

  • Attachment: Upload the required documents, screenshots or any reference files required for a step.

  • Click the "Add Step" button to add a new test step.

4. Define Test Case Details:

  • Specify the test case name and module and Save your test case. Learn how to organise and manage test cases here Organise your Test Cases.

  • Pre-requisites: Any setup or conditions required before executing the test case, you can mention them in the form of checklist.

  • User Story: If you are defining the test case for a user story, then you can select the user story. Learn more

  • Defect: If you are defining the test case for a defect, then you can select the defect in details section. Learn more

Purpose of Manual Testing

  • Uncovers defects: Manual testing can identify issues that automation might miss, especially those related to user experience.

  • Exploratory testing: Testers can deviate from the script to explore different scenarios and find unexpected issues.

  • Usability testing: Manual testing helps evaluate the software's user-friendliness.

  • Initial testing: Manual testing is often used as a starting point before automation is implemented.

Last updated