# Paths and Scenario Definition
## **Automation Model**
To establish an initial automation framework, a formal methodology must be followed to ensure an organized and repeatable procedure. This model, aligned with the testing types described earlier, serves as the foundation for implementing automated testing procedures across our clients' processes.
## **Templates**
Effective implementation of automated testing relies heavily on comprehensive documentation to uphold process integrity. Here are suggested templates that serve as simple yet integral examples utilized within our company:
**High-Level Process Description**
{% file src="" %}
**Process Paths Description**
{% file src="" %}
**Scenarios Template**
{% file src="" %}
## **Journey Paths on a Process**
When dealing with processes, it becomes important to identify the various paths that the workflow may take. Within an automated testing project, it is advisable to initiate testing by exploring the "Happy Path" within the process. The characteristics of a Happy Path can be identified by examining the following properties on a user journey:
## **Data Scenarios Configuration**
Paths represent the sequential tasks undertaken to complete an end-to-end journey within a process, defining where the test will occur. Conversely, a scenario encompasses elements that establish a status for the process, driven by specific data sets to achieve desired outcomes. These elements constitute a combination known as a "stimulus" and serve as input for the process to progress towards the expected output.
The creation and testing of multiple scenarios contribute to the consistency and reliability of our tests, ensuring thorough validation of our automation processes.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://processmaker.gitbook.io/quick-start-guides/processmaker-automated-testing/process-testing-automation/paths-and-scenario-definition.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
