probitas-run
Running and validating Probitas scenarios. Use when executing tests, running scenarios, or debugging test failures.
When & Why to Use This Skill
The probitas-run Claude skill is designed to streamline the execution and validation of Probitas testing scenarios. It empowers developers and QA engineers to automate test runs, apply sophisticated filtering via selectors, and perform deep-dive debugging on failed assertions. By integrating these capabilities directly into the Claude agent environment, it enhances software quality assurance workflows and accelerates the identification of regression issues.
Use Cases
- Automated Scenario Execution: Quickly run and validate complex Probitas test scenarios to ensure code changes meet functional requirements.
- Targeted Test Filtering: Use tag-based selectors to execute specific test suites, such as API tests, or exclude 'slow' tags to optimize development speed.
- Efficient Debugging and Troubleshooting: Utilize built-in validation checks and verbose/debug modes to pinpoint the root cause of test failures in environment variables or logic assertions.
- Regression Testing: Systematically run named scenarios during the development lifecycle to prevent new features from breaking existing functionality.
| name | probitas-run |
|---|---|
| description | Running and validating Probitas scenarios. Use when executing tests, running scenarios, or debugging test failures. |
Instructions
Run /probitas-run command (or /probitas-run <selector> with filter).
If project not initialized → run /probitas-init first.
Selector Examples
probitas run -s tag:api # Match tag
probitas run -s "!tag:slow" # Exclude tag
probitas run -s user # Match scenario name
If Tests Fail
- Run
/probitas-checkfor validation errors - Check error messages for assertion details
- Verify environment variables (API_URL, DATABASE_URL)
- Use
--verboseor--debugfor more output