Quickstart: web app

Use the web app when you want a visible path from repository context to a reviewable test and your first CI check.

1. Create your workspace and project

Sign up at QualityMax, then create a project for the application you want to verify. Give it the base address of a safe test environment if you plan to run browser tests.

2. Import a repository

Open the project and choose Import Repository. Paste the GitHub repository address and choose the branch you want to analyze. Public repositories can be imported directly; for a private repository, use the access flow presented by QualityMax rather than pasting credentials into source files or documentation.

QualityMax analyzes the repository and brings in existing supported test files. The project then has repository context, test cases, and automation scripts in one place.

3. Create a small generated test case

Open Test Cases in the project. Create or select one focused case for a stable, valuable journey, then generate its Playwright script. Review the case title, steps, expected result, and generated code before you run it.

For a first run, choose a journey with known test data and a clear expected result. Avoid destructive actions and third-party payment or email flows until you have a dedicated test setup.

4. Run it and inspect the result

Run the script from Executions. Wait for a terminal result, then open that execution. A passing result should show the status plus the evidence captured for the run, such as screenshots, video, logs, and a trace when available.

Do not treat a generated script as coverage until you have looked at this result. The execution view is where you verify that the test exercised the journey you intended.

5. Add your first CI gate

With the repository linked, add the QualityMax GitHub Action to that repository:

1. In QualityMax, open Settings → API Tokens and create a token.

2. In GitHub, save it as the repository secret QUALITYMAX_CREDENTIAL. Never put the token in the workflow file.

3. Add this workflow as .github/workflows/qualitymax.yml, replacing the project identifier:

   name: QualityMax
   on: [pull_request]
   
   jobs:
     test:
       runs-on: ubuntu-latest
       steps:
         - uses: actions/checkout@v4
         - uses: Quality-Max/qualitymax-github-action@v1
           with:
             api-key: ${{ secrets.QUALITYMAX_CREDENTIAL }}
             project-id: 'your-project-id'
             test-suite: smoke

Tag the reviewed test smoke, open a small pull request, and wait for the QualityMax job to finish. The job provides the pass/fail signal and a link back to the QualityMax execution. If the action reports that no tests matched, confirm the tag and project identifier before treating the gate as complete.

Your first loop is now complete: signup, repository import, generated test case, a CI gate, and an inspectable execution artifact or trace. Expand coverage one journey at a time.

Prefer to drive the same workflow conversationally? See the MCP quickstart.