OpenParable
Skip to content
← Back to skills

Testing Steps

Testing & Quality
testing-steps

Testing Steps is an Agent Skill for testing & quality published in the dradis/dradis-ce repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Generate acceptance testing steps after completing a feature or bug fix. Use when the user asks for testing steps, a testing plan, or how to test something.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/dradis/dradis-ce/blob/HEAD/.claude/skills/testing-steps/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/testing-steps, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Based on the work done in this conversation, generate an acceptance testing plan for the Support / Customer Success team.

The plan must follow this exact format:

Testing steps

A numbered list of steps where each step is either:

  • An action: what the tester does (e.g. "Navigate to...", "Login as...", "Create a...", "Edit a...", "Delete a...", "Click on...")
  • An assertion: what the tester verifies (e.g. "Assert the record was deleted", "Assert the error message appeared", "Assert the flash message reads...")

Rules:

  • Begin with any prerequisite steps (login, seed data, navigation to starting point)
  • Cover the happy path first, then edge cases and error states
  • Every action that changes state should be followed by an assertion
  • For API-related features include a curl example step with the expected response
  • Steps must be specific enough for someone unfamiliar with the codebase to follow in a browser — no ambiguity
  • Do not add explanations or commentary outside the numbered list