SkillsAdd

stellar/laboratory · Archived

test-changed

Run e2e and unit tests related to files changed on the current branch. Use after making code changes to verify nothing is broken.

First seen Jun 22, 2026

Installation

$ npx skills add stellar/laboratory --skill test-changed
View on skills.sh ↗ GitHub repository ↗

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

zustand-store-patterns Same source
stellar/laboratory

Reference for the two Zustand store patterns in Stellar Lab — main store (querystring) and tran…

1 installs
react-rerender-mental-models Same source
stellar/laboratory

Correct mental models for React re-renders and memoization. Use this skill when writing, review…

1 installs
commit-progress Same source
stellar/laboratory

Commit a logical unit of work with a descriptive message. Invoke after completing a meaningful …

1 installs
webapp-testing Similar · more installs
anthropics/skills

Toolkit for interacting with and testing local web applications using Playwright. Supports veri…

152.3K installs

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

agent-browser Same topic
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
azure-diagnostics Same topic
microsoft/azure-skills

Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe …

568.9K installs
azure-validate Same topic
microsoft/azure-skills

Pre-deployment validation for Azure readiness. Run deep checks on configuration, infrastructure…

567.7K installs
azure-aigateway Same topic
microsoft/azure-skills

Configure Azure API Management as an AI Gateway for AI models, MCP tools, and agents. WHEN: sem…

566.3K installs
azure-compute Same topic
microsoft/azure-skills

Azure VM/VMSS router. WHEN: create / provision / deploy / spin-up VM, recommend VM size, compar…

510K installs
supabase-postgres-best-practices Same topic
supabase/agent-skills

Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill …

391.6K installs

Also in this package

Other skills from stellar/laboratory.

npx skills add stellar/laboratory
zustand-store-patterns 1 react-rerender-mental-models 1 commit-progress 1

Browse all from stellar/laboratory

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 109
License LICENSE
Default branch main
Open issues 42
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,347 B
  • docs SUMMARY.md 149 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

Run Tests for Changed Files

Run e2e and unit tests that are relevant to the files changed on the current branch.

Test Configuration

  • Unit (Jest): Config in jest.config.js, path aliases via moduleNameMapper
  • E2E (Playwright): Config in playwright.config.ts, Chromium only, 20s timeout per test, 2 retries, 2 workers
  • E2E dev server: Playwright starts pnpm dev automatically, but reuseExistingServer: true in non-CI — a stale server from another branch will cause false failures

Steps

  1. Kill any stale dev server on port 3000 before running e2e tests. Playwright's reuseExistingServer will pick up a server from a different branch otherwise, causing false failures (especially in worktrees):

``bash lsof -ti:3000 | xargs kill -9 2>/dev/null; true ``

  1. Find changed files relative to main:

``bash git diff --name-only main...HEAD git diff --name-only # unstaged git diff --name-only --cached # staged ``

  1. Map source changes to test files. Use these rules:

- src/app/(sidebar)/transaction/build/ -> tests/e2e/buildTransaction.test.ts, tests/e2e/savedTransactions.test.ts, tests/e2e/urlParams.test.ts - src/app/(sidebar)/transaction/sign/ -> tests/e2e/signTransactionPage.test.ts - src/app/(sidebar)/transaction/submit/ -> tests/e2e/submitTransactionPage.test.ts - src/app/(sidebar)/transaction/simulate/ -> tests/e2e/simulateTransactionPage.test.ts - src/app/(sidebar)/transaction/fee-bump/ -> tests/e2e/feeBumpTransactionPage.test.ts - src/app/(sidebar)/account/fund/ or src/app/(sidebar)/account/create/ -> tests/e2e/fundAccountPage.test.ts, tests/e2e/createAccountPage.test.ts - src/app/(sidebar)/xdr/ -> tests/e2e/viewXdrToJsonPage.test.ts, tests/e2e/jsonToXdrPage.test.ts - src/app/(sidebar)/endpoints/** -> tests/e2e/endpointsPage*.test.ts - src/app/(sidebar)/smart-contracts/** -> tests/e2e/contractExplorer*.test.ts - Shared code — run ALL e2e tests: src/components/, src/helpers/, src/hooks/, src/store/, src/constants/, src/types/, src/validate/, src/styles/, src/middleware.ts - tests/e2e/mock/** -> run ALL e2e tests that import from mock/ - tests/e2e/*.test.ts changed directly -> run those tests - tests/unit/** changed -> run unit tests - If source files under src/helpers/ or src/validate/ changed, also check tests/unit/ for matching unit tests

  1. If XDR encoding or transaction building logic changed (e.g. ClassicTransactionXdr.tsx, SorobanTransactionXdr.tsx, src/helpers/xdr/), hardcoded hash/XDR values in tests may need updating. Flag this to the user before running tests.
  1. Run the identified tests:

- E2E: npx playwright test <file1> <file2> ... --retries=0 --reporter=list - Unit: pnpm test:unit <file> - If no specific tests identified, run the full suite: pnpm test:e2e and pnpm test:unit

  1. Report results. Show pass/fail counts and list any failures with their error messages. For failures, read the relevant test code and source code to suggest fixes.