I have a repo

For a repository owner, the shortest useful loop is import, generate, run, and gate. Start with one user journey that matters to a pull request rather than trying to automate every path at once.

Import the repository

The web app quickstart covers the repository workflow: sign in, choose Import Repository, select the repository, and create a project. The project becomes the container for the test cases and automation scripts that QualityMax tracks.

Keep the imported scope deliberate. A focused project makes it easier to connect a generated test to a real repository change and to distinguish useful failures from unrelated application instability.

Generate and review a test

In the same web app quickstart, generate test cases from a selected journey and inspect the generated script before running it. Generation accelerates the first draft; it does not remove the need to review the behavior, assertions, and test data assumptions.

The core concepts describe the hierarchy behind that workflow: a project contains test cases, and a test case can have one or more automation scripts. This lets you keep the business scenario stable while revising its implementation.

Add a CI gate

After a test has produced trustworthy evidence, add a CI gate using the web app quickstart. The core concepts describe the available pull-request gate types and which ones block versus advise. Start with the smallest gate that verifies the risk you are trying to control, then make its result visible in code review.

Suggested first session

1. Import a repository and create a project for one service or application.
2. Generate and review a test for a stable, high-value journey.
3. Run it, inspect the trace and result, then add the appropriate CI gate.