1. Overview

2. Creating a manual test case

1. Navigate to the Test Cases tab from the left panel.
   
   
   
   
2. Create a test case in your desired test platform: Web, Android, or iOS.
3. Switch the testing type to Manual to begin writing the test case manually.
   
   

Note: Alternatively, you can use Zia to generate manual test cases automatically. Provide a scenario or requirement description, and Zia will suggest structured test cases with conditions and steps, which you can further refine. Learn more

4. Enter the following details in the Test Conditions section:
   1. Pre-Conditions: Define any conditions that must be met before the test begins.
   2. Post-Conditions: Define the expected state after the test completes.
   3. Attachments: Drag and drop files or click Browse Files to add supporting resources.
      
      

Note: Files can be uploaded in the Attachments and within individual cells in the Test Steps section. Each file must not exceed 2 MB, and you can upload a maximum of 20 files per test case.

5. Define the Test Steps. You can format the steps using the rich-text toolbar and include media (e.g., screenshots, input values). At least one test step is required to save a manual test case.
   1. Click inside the Action field to describe each test step.
   2. Enter related Test Data for each step.
   3. Specify the Expected Result.
   4. Use the + icon to add additional steps.
      
      
      
      
6. Click Save.

3. Managing manual test cases

You can add, edit, or delete steps directly within a manual test case using the inline or expanded editor.

1. Navigate to the Test Cases tab and select the test case you want to modify.
   
   
   
   
2. To edit the test conditions or test steps:
   1. Click inside the respective field, such as Pre-Conditions, Attachments, Post-Conditions, Action, Test Data, or Expected Result, to make inline edits.
   2. Use the maximize icon {} to switch to the full-screen editor for detailed updates or to add attachments.
      
      
      
      
   3. Make the required changes and click Save.
      
      
      
      
3. To add a new step:
   1. Click the + icon at the end of the step row to insert a new step.
      
      
      
   2. Alternatively, in the expanded editor view, click + Add Test Step to insert steps while editing in full-screen mode.
      
      
      
      
4. To delete a step:
   1. Click the Delete icon at the right side of the step row.
      
      
      

After creating your test cases, organize them into cohesive test suites based on functionality or test objectives. These suites are then incorporated into a broader test plan, which can be executed either manually by a tester or scheduled for automatic execution. When a test plan runs, automated test cases execute automatically in the order they were added. Manual test cases, however, will remain in the Yet to Start status, indicating that tester action is required to complete their execution within the plan.

3.1 Import manual test cases

You can import to migrate test cases from other QEngine projects or external sources. This also allows bulk updating existing test cases in your project. Importing is a two-step process. In the first step, you define how your test case steps are structured in the file, set your preference for handling duplicates, and upload the file. In the second step, you map your file's columns to the corresponding QEngine fields and start the import.

Step 1: Configure the file to start import

1. Click Import. In the popup that appears, you can configure the file structure, upload settings, and duplicate-handling preferences for the file to be imported.
   
   
   
   
2. Select a file structure to tell QEngine how your test case steps are organized in the file, so it can parse and import the data correctly:
   
   
   
   
   1. Multiple rows per test case - Each action, test data, and expected result is listed across multiple rows for each test case.
   2. Single row per test case - Each test case occupies a single row, with all actions, test data, and expected results contained within individual cells.
      
      
      
      Each option has its own Sample Template you can download as a reference for the expected file format, or as a starting point for preparing your data.
      
      Note: The file must follow the sample template structure exactly. Use the downloaded template directly instead of recreating it. Only the first sheet in the file is considered for import.
3. If you have selected Single row per test case, choose the delimiter used to separate test steps in your file. The available options are:
   1. Numbered list (1., 2., 3...n.)
   2. Parentheses list (1), 2), 3)...n)
   3. New line (\n)
      
      
      
      
4. Under Source File, click Browse to upload your file. Supported formats are .csv, .tsv, and .xlsx, with a maximum file size of 5MB.
5. Choose how QEngine should handle test cases in your file that already exist in your project:
   
   
   
   
   1. Skip duplicates - Duplicate test cases are ignored and will not be imported. Only new test cases are added to your project.
   2. Overwrite existing - Replaces your existing test cases with the version from the imported file.

Note: If your file contains duplicate test cases, only the last occurrence will be imported.

7. Click Next to proceed to the Map Fields stage.

Notes:

1. Any modules listed in your file that do not exist in QEngine will be created automatically during import.

2. Use a unique link name to distinguish between test cases or modules with identical names.
   

Step 2: Map fields

8. Map the columns from your source file to the corresponding QEngine fields. Fields marked with an asterisk (*) are required. QEngine will automatically match fields where a clear match is found in your file. Review the auto-mapped fields and adjust them as needed.
   
   
   
   
9. Use the Source File Column dropdown next to each QEngine field to select the corresponding column from your file.
10. Click Import to begin importing your test cases. Click Previous to go back and reconfigure the file if needed.

Now, the import runs in the background. Once it's complete, a summary is displayed showing the count of successfully imported and skipped test cases along with the reasons for skipping.

Note:

1. Importing may take a while depending on the size of your file. You can stay on the page to view the summary once it's complete, or leave and check back later, the import will continue in the background.
   
   

2. If the import fails, you can click Try Again to retry. For server-side errors, contact support at support@zohoqengine.com for assistance.
   

3.2 Export manual test cases

You can export your manual test cases to back up your data or share it outside QEngine. The exported file will be in .xlsx format.

1. Click Export.
   
   
   
   
2. Select a file structure. Choose how test case steps should be structured in the exported file:
   
   
   
   
   1. Multiple rows per test case - Each action, test data, and expected result is placed in its own cell across multiple rows.
   2. Single row per test case - Each test case occupies a single row, with all actions, test data, and expected results contained within individual cells.
      
3. If you selected Single row per test case, choose the delimiter used to separate test steps in your file. The available options are:
   1. Numbered list (1., 2., 3...n.)
   2. Parentheses list (1), 2), 3)...n)
   3. New line (\n)
      
      
      
4. Optionally, enable Password Protection to secure the exported file. Enter a password with a minimum of 6 characters.
   
   
   
   
   Tip: A strong password includes uppercase and lowercase letters (A–Z, a–z), digits (0–9), and special characters.
5. Click Export. Once complete, the file downloads automatically.

4. Executing a manual test case in a test plan result

When a test plan is initiated, either manually triggered or scheduled, it appears under the <Results> tab with a status of running. Automated test cases begin execution automatically, while manual test cases require tester input to record outcomes.

Tip: You can configure notifications during test plan creation to alert testers at any stage of execution, such as when a plan starts, completes, succeeds, or fails, or when certain test cases have not been executed. This ensures testers are informed if manual test cases are still pending and require further action. Learn more

1. Navigate to the Results tab and locate the running test plan.
   
   
   
   
2. Go to the Manual tab to view pending manual test cases from the list of test cases.
   
   
   
   
3. Select the desired manual test case to begin testing.
   
   
   
   
4. Click Start to initiate the timer.
   
   
   
   
5. Use the Assignee dropdown to assign the test case to a user.
   
   

Note: Currently this assignment is informational only and not yet part of review or approval flows.

You can record the execution result using any of the following methods, depending on how you want to validate the test.

Execute and mark test steps individually

You can use this when each step needs to be verified individually:

6. Review the test conditions and any attached files.
7. Under Test Steps, choose a step to begin execution.
8. For each step:
   1. Review the Action, associated Test Data, and the Expected Result.
   2. Compare the actual result with what was expected.
   3. Mark the status of the test step:
      1. Passed - The step was executed successfully and met the expected outcome.
      2. Failed - The step did not produce the expected outcome.
      3. Blocked - The step couldn't be executed due to a system issue or unmet dependency.
   4. Add comments under the Your Comments tab if needed.
      
      
      
      
9. After testing, you may stop the timer.
10. Click Save & Next Step to proceed step-by-step.
    
    Continue this until all required steps are validated. Once all steps are marked, the test case status is automatically derived based on the step results. If any step is marked Failed or Blocked, the test case is treated as a failed outcome in the Results page. Only when all steps are Passed is the test case marked Passed. You can also change this status manually if needed.
11. Once execution is complete, click Save to finalize.
    
    

Execute and mark test steps in bulk

You can use this when the results for multiple steps are already known, or detailed step-by-step validation isn't necessary.

12. Select multiple steps from the Test Steps list.
    
    
    
13. Choose the required status - Passed, Failed, or Blocked.
14. Apply the status to the selected steps.
15. Click Save.

Execute and mark the overall status of the test case

Use this when you already know the final outcome and want to record it directly.

16. Select the desired status from the overall test case Status option at the top-right corner.
    
    
    
    
    1. Choose how the status should apply:
       
       
       
       
       1. This Environment - Applies to the specific platform configuration under which the test case instance is being run.
       2. All Environment - Applies to all the associated platform configuration for which the test case is being run.
          
          This overrides step-level validation, and any unmarked steps are considered not tested.
          
          
    2. Click Save.
       

Similarly, at the test case level, you can bulk-update the status of multiple manual test cases from the Manual tab and update their status in bulk.

Once saved, the selected status for each step is recorded within the test case results and contributes to the overall outcome of the test plan.

Upon completion of manual test cases, the results page provides a detailed breakdown of outcomes for each test case, offering clear insights into progress and quality metrics.

5. Related links

1. Test cases
2. Web testing
3. Mobile testing
4. Test suites
5. Test plans
6. Results

6. What's next