Generating Test Scenarios and Test Execution Guide

WebCoPilot provides a seamless way to generate and execute test scenarios using a combination of various inputs, enabling robust and versatile testing capabilities.

Generating Scenarios

You can generate test scenarios using various inputs in WebCoPilot.

❗ Important To generate test scenarios, use the term generate in the input field, followed by your request.

Below are the supported inputs and combinations:

1. Using Just Web Page URLs

• Input the URL of the application you want to test.

• Example Prompt:

   Generate test scenarios for www.google.com.

Video Demo

Refer to the video below for a complete walkthrough of generating test cases:

---

2. Using JIRA Tickets

To generate test scenarios using JIRA tickets, ensure your JIRA integration is set up correctly before proceeding. Follow these steps:

---

Step 1: Configure JIRA Configurations

Ensure that your JIRA account is set up with the required credentials.

👉 Refer to the guide: Setup Jira Configuration Step-by-Step

Step 2: Generating Test Scenarios Using JIRA Tickets

Once JIRA is successfully configured, you can generate test scenarios by mentioning the JIRA ticket ID properly.

• Example Prompt:

  Generate test scenarios for jira ticket MON-5

Video Demo

Refer to the video below for a complete walkthrough of generating test cases using JIRA :

📝 Note Ensure you use the term JIRA ticket while providing the ticket ID. If this term is not mentioned correctly, the system might fail to generate scenarios, leading to inaccuracies

---

3. Using Confluence Links

Leverage Confluence links to generate test scenarios seamlessly. Before starting, ensure your JIRA integration is configured properly. Follow the steps below to get started.

Step 1: Configure JIRA Integration

Ensure that your JIRA account is set up with the required credentials and API access.

👉 Refer to the guide: Setup Jira Configuration Step-by-Step

Step 2: Generate Test Scenarios Using Confluence Links

Once JIRA is configured, proceed to use Confluence links to create detailed and actionable test scenarios. This step will ensure that your test scenarios align with the information stored in your Confluence documentation.

Example Usage:

Confluence Link: Understanding Amazon's Recommendation Algorithm

• Example Prompt:

  Generate tests for the Recommendation Algorithm described in the Confluence page: Understanding Amazon's Recommendation Algorithm

Video Demo

For a clear step-by-step guide, watch the demonstration video below:

This ensures you generate valid test scenarios, as shown in the example, focusing on the Recommendation Algorithm described in the documentation.

Handling Inappropriate Inputs

• Providing unclear input, such as "generate test for Confluence so-and-so link" or "generate test scenarios for this document", may result in irrelevant outputs.

Watch the example in the video below:

• In some cases, scenarios may be generated based on the Confluence web page itself rather than the specific data it contains.

📝 Note Ensure the following before generating test scenarios:

• Understand Document Correlation: Ensure the generated test scenarios directly correlate with the topics discussed in the Confluence document by at least mentioning the relevant heading.

• Provide Explicit Testing Instructions: Be specific about what needs to be tested. Generalized or vague inputs may result in irrelevant test scenarios.

• Attach the Confluence Link: Always include the link to ensure the generated scenarios are accurate and relevant based on it.

---

4. Using Files

Supported File Types:

• PDF

• TXT

• Markdown

• RTF

Example Prompt:

  Generate test cases for Salesforce CRM Content  

Video Demo

• In the video above, a PDF file related to Salesforce is used, and the input specifies generating test cases for Salesforce CRM Content.

• If the input provided is vague, such as "Generate test cases for the uploaded file" without specifying the content or feature in the uploaded file, it may result in irrelevant or incomplete test scenarios, as shown in the example:

TestPilot

📝 Note Always specify what to generate test cases for, ensuring the input clearly aligns with the content of the uploaded file , as misalignment may result in irrelevant or incomplete test scenarios

Exporting Generated Test Scenarios

After generating test scenarios, you can export the specified test or all generated test scenarios.

Steps:

1. Click on the Export Scenarios button.

   

   TestPilot
2. From the dropdown, select the Team, then choose the Project and Module.

   

   TestPilot
3. A list of the generated scenarios will be displayed. Select the scenarios you wish to export.

   

   TestPilot
4. Finally, click on the Execute Scenarios button to export the selected scenarios.

Executing Scenarios

To execute scenarios, use the term execute in your input request. The process supports two types of execution, Both yielding the same output.

❗ Important Only one scenario can be executed at a time.

Supported Actions

Supported actions for executing includes:

General Actions

• Launch

• Wait For Load

• Wait

• Switch Tab

• Set

Interaction Actions

• Click

• Right Click

• Clear

• Select

• Hover

• Send Keys

Verification Actions

• Verify HTML Title

• Verify Text

• Verify Text Contains

• Verify Element Present

• Verify Element Not Present

• Verify Element Visible

• Verify Element Not Visible

• Verify Element Enabled

• Verify Element Disabled

This structure ensures clarity and better organization for executing scenarios effectively.

1. Generated Scenario-Based Execution

This type of execution is based on scenarios generated in advance.

• Prerequisite: Ensure test scenarios are generated before initiating execution.

• Execution Scope: Specify the scenario to execute using its number or description. Example: "Execute scenario 1" or "Execute scenarios for [specific feature]".

• Limitation: Simultaneous execution of all scenarios is not supported.

---

2. Individual Execution

Execute tests without relying on predefined scenarios. This approach allows you to directly run individual tests.Here You can execute your own custom scenarios directly, without needing pre-generated ones.

---

Execution Output

The output for Both execution types includes:

• Details:

  • Test case name

  • Step number

  • Action performed

  • Data used

  • Status of the test

• Live Screenshot: Captured during the execution process for better traceability.

---

Video Demo

Scenario-Based Execution

The video below demonstrates executing a single scenario after generating test scenarios:

Individual Execution

The video below shows the process of executing individual tests:

📝 Note

• Only one scenario can be executed at a time.

• Simultaneous execution of all scenarios is not supported in scenario-based execution.

• Specify the exact scenario or test to be executed for accurate results.

Exporting Tests

After executing the tests, you can export the executed tests.

Steps:

1. First, click on the Export Test button.

   

   TestPilot
2. From the dropdown, select the Team, then choose the Project and Module.

   

   TestPilot
3. In the Script Name input field, enter the name of the script.

4. In the Objective field, write the objective for the test.

5. Finally, click on the Export Test button to export the executed test.

   

   TestPilot

Enhancing Bug Reporting with JIRA Integration

This step revolutionizes bug management by enabling effortless and efficient reporting of failed test steps.

Step 1: Configure JIRA Integration

Ensure that your JIRA account is set up with the required credentials and API access.

👉 Refer to the guide: Setup Jira Configuration Step-by-Step

Step 2: Trigger Bug Report Creation

When a test step fails, initiate the bug reporting process within your testing environment.

1. Locate the bug symbol next to the step description indicating a failed step.

   

   TestPilot
2. Click on the bug symbol.

3. A dropdown will appear to select a JIRA board.

   

   TestPilot
4. After selecting the board, you'll see pre-filled Summary and Description fields with minimal manual input required.

5. Review the information and click on the Add Bug button to push the bug to your JIRA board.

   

   TestPilot

❗ Important For cross-functional teams, provide clear labels (e.g., “Critical” or “UI Priority”) during export to ensure the right team takes action.

Through this optimize your workflow by turning test failures into actionable bugs in seconds, boosting Both speed and accuracy!

Advanced Feature: Multi-Instruction

This feature simplifies your workflow by enabling test generation and execution in a single instruction, allowing seamless execution across multiple websites with automatic scenario generation.

Key Highlights:

• Supports multi-instruction capabilities, enabling simultaneous test generation and execution.

• Generate test scenarios from diverse sources, such as:

  • Web URLs

  • Confluence documentation

  • JIRA tickets

  • Attached files

• Execute test scenarios against real-time web applications by providing the relevant URLs.

• Example Prompt:

    Execute Search for Louis Vuitton in
    www.snapdeal.com
    www.ajio.com
    www.flipkart.com and generate test scenarios for each.

Video Demo

📝 Note

• When specifying multiple URLs, list each URL on a new line for better clarity and readability.

• The system supports flexible workflows as you can generate and execute test scenarios in any order

• You can execute custom scenarios or scenarios generated by the system, based on your requirements.

---

Return to WebCoPilot Documentation.