Course: CI and releases — 1. Course overview
A hands-on course on testing every deploy: a pipeline that signs in with an API token, runs a suite, waits for the result and stops a release that breaks it. Then you label runs with the release they tested, and read the release evidence report that says whether a version can go out.
Modules
Section titled “Modules”| Module | What you learn | Length |
|---|---|---|
| 1. This page | What the course covers, and what you need | 5 min |
| 2. API tokens for CI | Creating and revoking tokens, plan limits, acting as a pipeline, what a token can and cannot reach | 17 exercises |
| 3. Suite runs, schedules and failure emails | Running and stopping a suite, schedules and plan limits, failure and recovery emails, atx run --suite |
2 h |
| 4. Tests running at the same time | How many tests run at once on each plan, and why runs above the limit wait in a queue | 14 exercises |
| 5. Run after deployment, notifications and MCP | A pipeline played from PowerShell, deploy details, who is emailed, the self-healing review digest, an AI assistant running suites | 75 min |
| 6. Release metadata | Release, build and commit on a suite run; what the CLI reads from CI; what is deployed on an environment | 1 h |
| 7. Release evidence report | Go, Go with risks, No-go and not enough evidence; comparing with the release before; which failures hold a release | 75 min |
Do the modules in order: later modules use the tokens and suites of earlier ones.
Who it is for
Section titled “Who it is for”- DevOps and release engineers who add AutoTestX to a pipeline: modules 2, 3, 5 and 6.
- Test managers and QA leads who decide whether a release goes out: modules 3, 6 and 7.
- Administrators who choose the plan: modules 2 and 4.
What you need
Section titled “What you need”- An AutoTestX account with the Admin or Test Manager role in a practice project.
- A platform administrator for the exercises that change the organization’s plan. On your own server this is the account claimed at First sign-in.
- PowerShell: it plays the part of the pipeline.
- A second person with the Tester role, for one exercise of module 3.
- For module 7, your own installation (Deployment), because the browser that runs your tests has to reach the demo application.
Learning objectives
Section titled “Learning objectives”By the end you can:
- create a token for a pipeline, keep it safe, and revoke it;
- run a suite from a pipeline and fail the pipeline when the suite fails;
- schedule a suite and explain what your plan allows;
- explain why a run says Queued, and when it will start;
- label a suite run with its release, build and commit;
- read a release evidence report and defend its recommendation.