Run targeted e2e tests for UI changes by mapping git diffs to feature files.
npx skills add https://github.com/juspay/kolu --skill test-juspay
Please help me install this Agent Skill. Skill: test Source: https://github.com/juspay/kolu/tree/main/.apm/skills/test Command: npx skills add https://github.com/juspay/kolu --skill test-juspay
Run e2e tests scoped to the current branch's changes.
Run e2e tests for the current changes by triggering the e2e skill.
High-intent search queries and answers about installing and using this skill.
Run focused e2e tests for your changes by mapping git diff changed files to matching .feature files under packages/tests/features, executing only relevant scenarios via just test-quick. It skips execution automatically when changes are server-only with no UI impact.
Git diff mapping identifies changed files in packages/client and packages/tests, then matches them to corresponding .feature files to execute only relevant e2e scenarios using just test-quick, reducing test scope to directly affected UI features.
Yes, it applies to UI-related changes across packages/client and packages/tests. It discovers and maps changed files from these paths to feature files, but skips e2e execution if your branch modifications are entirely server-only.
Yes, triggering e2e tests requires git to diff changed files and just test-quick to execute the scoped scenarios. You also need access to packages paths for feature file discovery and change mapping.
E2e tests are skipped for backend modifications because the smart skip logic detects server-only changes with no UI impact, avoiding unnecessary test execution when packages/client and packages/tests are unaffected.
thoreinsteinAnalyze Go packages to identify gaps in test coverage without modifying code.
HerbertJulioReview changed files for architecture, types, security, and test coverage.
selfagencyAnalyze git status and diff to create Git Flow branches.
DataDogIdentify changed files and run affected test suites via scripts/run-tests.
