Conga Product Documentation

Welcome to the new doc site. Some of your old bookmarks will no longer work. Please use the search bar to find your desired topic.

Use Case: Test Case Execution

This use case executes an existing test case in Test Author and reviews the execution results for each test step.

Actor: Test Author User or QA Engineer

Objective: To execute an existing test case in Test Author and review the execution results for each test step

Scope: Test Author - Test Case Execution

Prerequisites:
  • A test case is created.
  • The required environment and user are configured
  • API access credentials or access token are available.
Post conditions:
  • The test case execution is completed.
  • Execution status and detailed results are displayed for review.
Step 1: Executing a Test Case
  1. On the Test Author home page, click test Case in the right pane or navigate to Design > Test Case in the left pane.
  2. Locate the required test case from the list of available test cases.
  3. Click More next to the test case name and click Test, or click the test case name to open it and then click Test. This starts the test case execution process.

  4. In the Execution panel, select the Environment for test execution and select the User.
    Note: In a multi-user setup, ensure that the correct Environment and User are selected to avoid execution errors
  5. If an access token is already generated, click the Paste icon to use the token.
  6. Click Run to start the test case execution.
Step 2: Reviewing the Execution Results
  1. After the test case execution is complete, review the status of each test step.
    • Green tick: Indicates that the test step is executed successfully.
    • Red cross: Indicates that the test step has failed.
    • Yellow triangle: Indicates that the test step was skipped.
  2. Review the Summary Panel, which displays the following:
    • Request and response details.
    • Assertion results and failures.
    • Error or failure messages if any.
Expected Outcome
  • The test case runs using the selected environment and user.
  • Execution results are clearly displayed, enabling quick validation and troubleshooting.