> For the complete documentation index, see [llms.txt](https://docs.appsurify.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appsurify.com/getting-started/getting-started.md).

# Getting Started

Easy to Install and Easy to Use

## 3 Requirements to be Successful

1. Access to Developer Repository(s)
2. Access to CI Pipeline
3. Access to Tests

### Why do I need these:

* **Developer Repository**: To Push Developer Commit Metadata so we can see where changes are made, and therefore, prioritize test execution based on those changed areas. 
* **CI Pipeline:** To connect the Tests and Pipeline for optimization, and to execute the prioritized tests based on a per build/change basis. 
* **Access to Tests:** The automated testsuites you'd like to Optimize for faster feedback to catch regressions earlier and more economically. 

## Get Started in Steps:  

1. [Sign up and Create Account](/getting-started/sign-up-and-create-account.md)
2. [Create Project](/getting-started/step-1-create-project.md)
3. [Connect Developer Repository](/getting-started/step-2-connect-repository.md)
4. [Connect Tests in CI Pipeline](/getting-started/step-3-connect-tests.md)
5. [Start Prioritizing Tests](/getting-started/start-prioritized-testing.md) 

## Integrations

[Prebuilt Integrations](/integrations/integrations.md)

## Smart Test Selection Explained

[How and why we select tests. ](/getting-started/working-knowledge/smart-test-selection-explained.md)\ <br>

## Next: [Sign up and Create an Account!](/getting-started/sign-up-and-create-account.md)&#x20;


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.appsurify.com/getting-started/getting-started.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.