test

Run backend and frontend unit tests in parallel across SEBT repositories.

10|1|Updated Nov 7, 2025
One-click install
npx skills add https://github.com/codeforamerica/sebt-self-service-portal --skill test-codeforamerica
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test
Source: https://github.com/codeforamerica/sebt-self-service-portal/tree/main/.claude/skills/test
Command: npx skills add https://github.com/codeforamerica/sebt-self-service-portal --skill test-codeforamerica

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Running unit tests across multiple SEBT repositories is tedious and error-prone when done serially. This Skill orchestrates parallel test execution to save time and ensure consistency across portals and connectors.

Core Features & Use Cases

  • Parallel test execution across portal, state-connector, dc-connector, and co-connector
  • Flexible scope: run all tests, backend only, frontend only, or a subset of repos
  • Automated reporting and summary of pass/fail counts for quick diagnosis

Quick Start

Invoke this skill with no arguments to run all backend and frontend tests across all SEBT repos.

Frequently Asked Questions about test

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

FAQPage Schema
How do I run unit tests across multiple repositories in parallel?

You can run unit tests across multiple repositories in parallel by invoking the skill to execute backend and frontend test suites simultaneously across portal, state-connector, dc-connector, and co-connector repos.

Can I run only backend or frontend tests for a specific repo?

Yes, you can configure the test scope to run backend only, frontend only, or a specific subset of SEBT repositories by setting the appropriate arguments during skill invocation.

What is the best way to automate parallel test execution for pnpm and dotnet projects?

Automating parallel test execution for pnpm and dotnet projects is handled by using separate Bash invocations per test suite, enforcing explicit repository paths to ensure consistent multi-repo testing.

How does parallel test execution summarize pass and fail counts?

Parallel test execution summarizes pass and fail counts by aggregating the results from each separate Bash invocation, returning a final summary that provides quick diagnosis across all executed test suites.

Do I need to specify repository paths when running multi-repo tests?

Yes, you need to specify repository paths because the skill enforces explicit repository paths for portal, state-connector, dc-connector, and co-connector to accurately execute and orchestrate the parallel test suites.