> For the complete documentation index, see [llms.txt](https://docs.sealights.io/knowledgebase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sealights.io/knowledgebase/setup-and-configuration/integrations/qtest-integration/commands.md).

# Commands

The SeaLights qTest Integration Tool provides the following commands. All commands are run from the project root directory.

| Command                                                                                                                                | Purpose                                                         | When to Use                                                                  |
| -------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------- | ---------------------------------------------------------------------------- |
| [`npm run setup`](/knowledgebase/setup-and-configuration/integrations/qtest-integration/commands/setup.md)                             | Interactive setup wizard                                        | First-time configuration, reconfiguration, or adding new test stage mappings |
| [`npm run report`](/knowledgebase/setup-and-configuration/integrations/qtest-integration/commands/report.md)                           | Extract test executions from qTest and report to SeaLights      | On a regular schedule (daily or per test cycle)                              |
| [`npm run recommendations`](/knowledgebase/setup-and-configuration/integrations/qtest-integration/commands/recommendations.md)         | Apply Test Optimization recommendations from SeaLights to qTest | Before a test execution cycle                                                |
| [`npm run manage-user-mapping`](/knowledgebase/setup-and-configuration/integrations/qtest-integration/commands/manage-user-mapping.md) | Manage user → lab ID assignments                                | After discovering new testers in qTest                                       |
| `npm run build-cache`                                                                                                                  | Pre-build the Test Design module cache                          | When test cases have moved to different folders in qTest                     |

{% hint style="info" %}
Add `-- --help` to any command to see its available options. For example: `npm run report -- --help`
{% endhint %}

{% hint style="info" %}
Add `-- --debug` to any command to enable verbose logging. Debug output is also sent to SeaLights for support purposes.
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sealights.io/knowledgebase/setup-and-configuration/integrations/qtest-integration/commands.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.