Data & Technical specialist
Default Kona assistant
QA & Test Engineer
Creates risk-based test plans, cases, and release confidence checks.
When to use it
A focused role with a visible finish line.
Best for: technical and analytics teams that need reproducible analysis, implementation, or quality work.
Expected outcome: an inspectable technical deliverable with assumptions, tests, and reproducible steps.
- A focused qa, testing, quality task where the expected decision or deliverable is clear.
- Recurring work that benefits from the same answer, assumptions, risks structure each time.
- A team that wants QA & Test Engineer available in direct chat, inline @mentions, and bounded Workspace tasks.
Configured instruction
“Build a risk-based test strategy. Cover critical paths, boundaries, permissions, data integrity, accessibility, regression, and observability. Make each test reproducible with a clear expected result.”
This instruction is part of the shipped default profile—not a generic prompt assembled for this page.
Workflow
How QA & Test Engineer approaches the work
- 01
Frame the outcome
State the decision, audience, deadline, constraints, and what a useful an inspectable technical deliverable with assumptions, tests, and reproducible steps looks like.
- 02
Ground the work
Provide relevant schemas, code, logs, event definitions, environments, constraints, and expected behavior. Label supplied facts, working assumptions, and unresolved unknowns.
- 03
Build the contracted output
QA & Test Engineer follows its markdown output contract and covers answer, assumptions, risks, next evidence.
- 04
Verify before use
Run the profile's quality checks, expose evidence gaps, and route high-impact low-risk conclusions to human review.
Capabilities
What the profile can use
- Knowledge grounding
- Structured deliverables
- Verification pass
- Analysis and code
Enabled tool families: code. Runtime availability still depends on account configuration, permissions, and the task.
Output contract
What a complete response must contain
The contract improves consistency; it does not make an answer automatically correct. Kona still marks assumptions, evidence gaps, and review requirements.
Prompt examples
Start with context and a decision
Prompt 1
Act as my QA & Test Engineer. Build a risk-based test strategy. Cover critical paths, boundaries, permissions, data integrity, accessibility, regression, and observability. Make each test reproducible with a clear expected result. Start by listing the missing inputs that would materially change the result.
Prompt 2
Use the QA & Test Engineer workflow for this qa task: [describe the situation]. Audience: [who will use it]. Constraints: [time, budget, policy, or data]. Return answer, assumptions, risks, next evidence.
Prompt 3
Review this draft as the QA & Test Engineer: [paste draft]. Check it against the stated evidence, identify unsupported claims or missing assumptions, and return a prioritized correction list.
Related specialists
Put QA & Test Engineer to work.
Use the default profile or fork it into a version your team controls.