Tutorials

Overview

End-to-end learning paths for QA engineers, developers, SREs, and administrators. Tutorials combine multiple Console areas into progressive lessons with estimated duration.

Complete tutorials in order when onboarding a new role. Individual guide pages provide single-task focus when you need a quick reference.

Tutorial tracks

• QA engineer track - projects, cases, runs, Test Health (approx. 4 hours)
• Developer track - CLI, API, CI integration (approx. 3 hours)
• SRE track - schedules, topology, reliability scores (approx. 3 hours)
• Administrator track - users, roles, integrations, audit (approx. 2 hours)

Choose a tutorial by the artifact you need

Select a learning path that produces something your team can review: a requirements-to-results example, a deployment diagram, an access matrix, or a remediation review record. Agree the practice environment and completion criteria before beginning.

Use only resources you are authorized to modify and synthetic data where possible. Confirm product access and feature availability for the steps you intend to practice.

Review and clean up the exercise

At completion, explain the configuration, steps performed, outcome, and remaining limitations to another teammate. Repeat a small part of the exercise to check that the result depends on documented setup rather than an unrecorded manual step.

Remove temporary credentials, scheduled work, test records, and exported artifacts through the approved process. Preserve only the learning evidence your organization needs.

All tutorials