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

# Getting Started

![Qyrus Web Testing](https://239974709-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FycS61vFhJMvvtnJCrDJk%2Fuploads%2Fgit-blob-45d534a0f22df884040b393a112aac7ae76511af%2Fbanner.png?alt=media)

Qyrus Web Testing lets you automate the testing of a web application — building tests once, running them on real browsers, and reading what happened.

You do not need to write code.

### The path from nothing to a first result

1. **Sign in and open Web Testing.** Your organisation gives you the Qyrus address and an account. Once you are in, click **Services** and choose **Web Testing** under **WEB**. See [Projects and Project Home](/web-testing/project-creation/landing-page.md).
2. **Create a project.** It holds everything else. See [Creating a Project](/web-testing/project-creation/create-project.md).
3. **Add a module.** Modules group related tests — one per feature or screen works well. See [Test Repository](/web-testing/build/creatingmodule.md).
4. **Create a script and give it steps.** Each step is one action: open a page, click a button, check some text. See [Test Scripts](/web-testing/build/creatingscript.md) and [Test Steps](/web-testing/build/creatingsteps.md).
5. **Dry run it.** This tells you whether the test actually works, before you commit to anything bigger. See [Dry Run](/web-testing/run/dryrun.md).
6. **Run it properly**, from a [Sprint](/web-testing/run/sprintrun.md) or from [Test Lab](/web-testing/run/testlabrun.md).
7. **Read the report.** See [Reports](/web-testing/analyze/reports.md).

### How the manual is organised

The sections mirror the product's own navigation.

| Section                                                 | What it is for                                          |
| ------------------------------------------------------- | ------------------------------------------------------- |
| [Projects](/web-testing/project-creation.md)            | Creating and finding projects                           |
| [Build](/web-testing/build.md)                          | Writing tests — modules, scripts, steps, data, settings |
| [Run](/web-testing/run.md)                              | Executing them — dry runs, sprints, Test Lab            |
| [Analyze](/web-testing/analyze.md)                      | Reading results — reports, mind maps, tags              |
| [Advanced Features](/web-testing/advanced-features.md)  | Healer AI, visual testing, functions, import and export |
| [User Actions](/web-testing/user-actions/actiontype.md) | Reference for all 125 test step actions                 |
| [Integrations](/web-testing/integrations.md)            | Connecting Jira, TestRail, Xray and others              |
| [FAQ](/web-testing/faq/faq.md)                          | Common questions                                        |

### Words worth knowing

| Term            | What it means                                                                                   |
| --------------- | ----------------------------------------------------------------------------------------------- |
| **Project**     | The top-level container for your modules, scripts, suites, sprints and data                     |
| **Module**      | A folder of related test scripts inside a project                                               |
| **Test script** | One test, made of steps                                                                         |
| **Test step**   | One action — a click, an entry, a check                                                         |
| **User action** | What a step does. Every step has exactly one                                                    |
| **Element**     | One thing on a web page — a button, a text box, a heading                                       |
| **Locator**     | How a step says *which* element it means. See [Test Steps](/web-testing/build/creatingsteps.md) |
| **Test suite**  | A group of scripts run together                                                                 |
| **Sprint**      | A planned round of testing with a start and end date                                            |
| **Test Lab**    | Run suites on demand, without the sprint structure                                              |
| **Dry run**     | A quick check that a test works, while you are still building it                                |

### User flowchart

![The overall user flow](https://239974709-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FycS61vFhJMvvtnJCrDJk%2Fuploads%2Fgit-blob-6fc44eb2a3aa625b5ec0fa37e3a63e3e859f8017%2FUser_flowchart.jpg?alt=media)