Troubleshooting: a structured playbook for Web and API failures

Use this order every time a suite fails. Most issues are fixed in under a minute when you follow the order.

1. Read the lower-right log first. The log line that says FAIL is almost always the real problem. Do not start guessing until you have read the log.
2. Identify which step failed. Note the step number, action, and selector or endpoint.
3. Apply the right checklist below.

WEB checklist
- URL: did the browser actually land where you expected?
- Selector: does the selector still exist on the current page state?
- Action: is "type" used on inputs, "click" on buttons, "select" on dropdowns?
- Value mode: is the dataset key present in your dataset file?
- Wait: does the page need a brief stabilizer before the next step?
- Assertion: is the expected value correct, and is it pulled from the right source (dataset vs runtime)?
- Page boundary: was the new page scanned again after navigation?

API checklist
- Base URL is configured.
- Auth header is present and the token has not expired.
- Content-Type matches the body type.
- Body format is valid JSON if you are sending JSON.

For a much deeper playbook covering session reuse, branch/loop logic, capture/reuse mistakes, and WebDriver issues, ask the Intelligent Assistant for "troubleshooting deep dive".

The public guide stays intentionally high level. Open the Intelligent Assistant for click-by-click instructions, learning order, and practice ideas.