# A Quick Tour of QATTS

An automation project has 2 phase.

Phase 1: Building **Automation components** and test cases

Phase 2: Using automation to speed up QA cycle and maintenance of existing scripts&#x20;

For phase 1,  an automation engineer with&#x20;

* Good understanding of automation concepts.
* All [Objects](/automation/objects.md) and their respective properties&#x20;
* Basic experience using [locators](https://www.tutorialspoint.com/selenium/selenium_locators.htm) and automation action patterns&#x20;
* Bit of java syntax.&#x20;
* Access to Qatts Studio
* Action Methods ([Standard](/standard-actions-methods.md), [UI](/ui-action-methods.md) & [File](/file-action-methods.md) )
* Concepts of Data Driven Automation&#x20;
* Classification of Test Case into Functional, UI Checks or Scenario

For Phase 2, a typical QA engineer with good understanding of target application and high level understanding  of Qatts Terminology.


---

# 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://docs.qatts.com/getting-started-1/1.1-about-qatts/a-quick-tour-of-qatts.md?ask=<question>
```

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.
