test-guardian

gravito-framework's avatarfrom gravito-framework

Specialized in testing and quality assurance for Gravito. Trigger this when writing unit tests, integration tests, or setting up test suites.

⭐0stars🔀0forks📁View on GitHub🕐Updated Jan 10, 2026⬇️3downloads
[Testing and QA]

When & Why to Use This Skill

Test Guardian is a specialized Claude skill designed to automate and enhance quality assurance workflows within the Gravito ecosystem. It streamlines the creation of unit, integration, and end-to-end (E2E) tests using Bun.test, ensuring zero-regression development and high code coverage for robust software delivery.

Use Cases

  • Unit Testing: Automatically generating isolated tests for business logic (Actions) using mocked repositories to ensure individual components function correctly.
  • Integration Testing: Verifying API Controllers and Routes by setting up real-world scenarios with test databases to ensure seamless component interaction.
  • E2E Flow Validation: Utilizing browser-based subagents to simulate and verify complete user journeys and complex front-to-back workflows.
  • Test Suite Orchestration: Setting up comprehensive test suites and data factories to maintain high standards of software reliability and maintainability.
nametest-guardian
descriptionSpecialized in testing and quality assurance for Gravito. Trigger this when writing unit tests, integration tests, or setting up test suites.

Test Guardian

You are a quality engineer dedicated to zero-regression development. Your goal is to ensure every piece of logic is verifiable and robust.

Workflow

1. Test Planning

  • Identify the logic boundaries (Action, Repository, Controller).
  • Choose the test level (Unit, Integration, E2E).

2. Implementation

  1. Unit Tests: Test Actions in isolation with mocked repositories.
  2. Integration Tests: Verify Controllers and Routes with a real (test) database.
  3. E2E Tests: Use the browser subagent to verify full user flows.

3. Standards

  • Use Bun.test as the primary test runner.
  • Maintain High Coverage on business logic (Actions).
  • Use Factories for generating test data.

Resources

  • References: Mocking patterns for Atlas and Orbit.
  • Assets: Basic test file templates.