krishnakanthb13/antigravity_global_skills

test_runner

Executes the project's test suite, analyzes failures, and provides fix recommendations.

Voir la source

Mode d’emploi

  1. Copiez la commande et examinez le paquet avant de l’installer dans votre environnement agent.
  2. Consultez le document original pour les outils, identifiants et environnements requis.
  3. Décrivez les entrées et le livrable souhaité ; comparez la sortie aux sources.
npx skills add https://github.com/krishnakanthb13/antigravity_global_skills --skill test_runner

Avant de commencer

  • L’installation n’inclut ni abonnement au modèle, ni quota API, ni accès aux fichiers.
  • Étoiles et installations reflètent l’activité, pas un test indépendant de qualité ou de sécurité.
Document Skill original

Rendu depuis le dépôt source en conservant titres, exemples, code, tableaux, liens et images.

Test Runner

Use this skill to execute tests and understand why they might be failing.

Inputs

  • Test Command: (Optional) Override defaults (e.g., npm test -- -t "search").
  • Scope: Specific file or all tests.

Tooling Strategy

  • Use run_command to execute tests.
  • Use view_file to read failure logs or source code if tests fail.

Workflow

1. Execution

  • Command: Run the appropriate test command for the environment (e.g., npm test, pytest, python -m unittest).
  • Scope: Run all tests by default, or target a specific file if requested.

2. Analysis

  • Pass: If all green, celebrate! 🟢
  • Fail: If red 🔴, analyze the output:
  • StackTrace: Where exactly did it blow up?
  • Assertion: What was expected vs. what was received?
  • Diff: Visual comparison of the data mismatch.

3. Recommendation

  • If tests failed, provide a summary of the failure.
  • Suggest potential fixes or point to the line of code causing the regression.

4. Integrity

  • Ensure that the testing process didn't leave behind artifacts (temp files, database entries) unless intended for debugging.

E2E Testing Patterns (Advanced)

When running or debugging End-to-End (E2E) tests:

  • Isolation: Ensure tests run in complete isolation (dedicated test accounts/data). Do not run destructive tests against production.
  • Flakiness: Debug flaky tests by checking for race conditions, unstable DOM selectors, or implicit waits rather than explicit waits.
  • Tracing: Utilize artifacts (screenshots, video recordings, network traces) captured during CI/CD failures to reconstruct the test state.
  • Critical Journeys: Focus E2E tests on critical user journeys rather than exhaustive edge-case testing (which belongs in unit tests).
du même dépôt

Autres Skills

Tous les Skills