test

Run targeted e2e tests for UI changes by mapping git diffs to feature files.

47|9|Updated Mar 19, 2026

Search Tags:#automation #e2e #qa #tests #git-diff #feature-files #test-quick

Ready to run

npx skills add https://github.com/juspay/kolu --skill test-juspay

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Run e2e tests scoped to the current branch's changes.

Core Features & Use Cases

Identify changed files: Match changed files (via git diff) to .feature files under packages/tests/features/.
Selective execution: Run only the relevant scenarios using just test-quick.
Smart skip logic: Skip e2e if changes are server-only with no UI impact.

Quick Start

Run e2e tests for the current changes by triggering the e2e skill.

Frequently Asked Questions about test

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I run e2e tests only for my current git branch changes?▼

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.

How does git diff mapping work for selective test execution?▼

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.

Can I use this to test changes across multiple packages directories?▼

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.

Do I need git and just test-quick to trigger e2e test execution?▼

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.

Why are my e2e tests being skipped for backend modifications?▼

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.