Getting started
How an OSTaaS session works
The five stages of a testing session, from reproducing a problem to a validated result.
Every OSTaaS work session follows the same five stages. The visual story on the home page walks through a real example: a Keycloak identity server that failed to start.
1. Reproduce
We first reproduce the reported problem in a clean, isolated environment so we are certain the failure is real and not a local quirk. The session records the exact conditions and the failing behavior.
2. Test
Once reproduced, we run the relevant test cases against the environment. Each case passes, fails, or is skipped, and resource usage is tracked so performance regressions are visible.
3. Capture evidence
Screenshots, logs, and recordings are captured as evidence. Sensitive regions are redacted automatically before anything is stored. Evidence is what turns a claim ("it's fixed") into something you can verify.
4. Remediate
When a root cause is found, the session proposes a concrete fix — for example, a corrected configuration value — with a before/after diff and a plain-language finding.
5. Validate
Finally we re-run the checks against the fix. When every check passes, the session is marked validated and the evidence is retained for your records.
Where to see this in the product
- Live and past runs: Test runs
- Captured proof: Evidence
- Formal readiness summaries: Certifications
Last updated 2026-09-02