Create your first test

A good first test has a clear start, a small number of actions, and a visible result. It should answer one release question: does this core journey still work?

Choose the workflow

• Pick a high-value path that changes often.
• Prefer a test account with stable data and limited permissions.
• Define the exact success state before writing steps.
• Avoid broad exploratory instructions for the first test.

Write precise instructions

Name:
Invite a teammate from workspace settings

Steps:
1. Action: Open the workspace member settings.
   Expected result: The member management area is visible.
2. Action: Invite [email protected] as a member.
   Expected result: The invite is submitted successfully.
3. Action: Review the pending invitations.
   Expected result: [email protected] is visible with a pending status.

Select the right options

• Choose a credential when the workflow requires login.
• Use AI run type for browser-executed checks.
• Use Manual run type for coverage you want to track but execute outside Killbug.
• Set priority based on release risk, not implementation complexity.

Calibrate the first run

After the run finishes, review the failed step, screenshots, recording, and generated summary before changing the test. The first run often reveals missing context, unstable data, or an expected result that needs to be more observable.