Designing Tests
CloudAI-X/claude-workflow-v2
Designs and implements testing strategies for any codebase. An agent skill from CloudAI-X/claude-workflow-v2.
Conventions for Handsontable's Jest unit and TypeScript type tests: where files go, how to run them, mocking limits and when to write an E2E test instead.
Install Handsontable Unit Testing
$ npx skills add handsontable/handsontable --skill handsontable-unit-testing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install handsontable/handsontable handsontable-unit-testing --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/handsontable/handsontable.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/handsontable-unit-testing .claude/skills/handsontable-unit-testing && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "handsontable-unit-testing" agent skill from https://github.com/handsontable/handsontable/tree/develop/.claude/skills/handsontable-unit-testing into .claude/skills/handsontable-unit-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "handsontable-unit-testing", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/handsontable/handsontable/tree/develop/.claude/skills/handsontable-unit-testingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add handsontable/handsontable --skill handsontable-unit-testing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install handsontable/handsontable handsontable-unit-testing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/handsontable/handsontable.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/handsontable-unit-testing .agents/skills/handsontable-unit-testing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "handsontable-unit-testing" agent skill from https://github.com/handsontable/handsontable/tree/develop/.claude/skills/handsontable-unit-testing into .agents/skills/handsontable-unit-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "handsontable-unit-testing", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add handsontable/handsontable --skill handsontable-unit-testing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install handsontable/handsontable handsontable-unit-testing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/handsontable/handsontable.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/handsontable-unit-testing .cursor/skills/handsontable-unit-testing && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "handsontable-unit-testing" agent skill from https://github.com/handsontable/handsontable/tree/develop/.claude/skills/handsontable-unit-testing into .cursor/skills/handsontable-unit-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "handsontable-unit-testing", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/handsontable/handsontable.git --path .claude/skills/handsontable-unit-testing--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add handsontable/handsontable --skill handsontable-unit-testing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install handsontable/handsontable handsontable-unit-testing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/handsontable/handsontable.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/handsontable-unit-testing .gemini/skills/handsontable-unit-testing && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "handsontable-unit-testing" agent skill from https://github.com/handsontable/handsontable/tree/develop/.claude/skills/handsontable-unit-testing into .gemini/skills/handsontable-unit-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "handsontable-unit-testing", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install handsontable/handsontable handsontable-unit-testingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add handsontable/handsontable --skill handsontable-unit-testing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/handsontable/handsontable.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/handsontable-unit-testing .github/skills/handsontable-unit-testing && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "handsontable-unit-testing" agent skill from https://github.com/handsontable/handsontable/tree/develop/.claude/skills/handsontable-unit-testing into .github/skills/handsontable-unit-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "handsontable-unit-testing", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add handsontable/handsontable --skill handsontable-unit-testing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install handsontable/handsontable handsontable-unit-testing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/handsontable/handsontable.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/handsontable-unit-testing .opencode/skills/handsontable-unit-testing && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "handsontable-unit-testing" agent skill from https://github.com/handsontable/handsontable/tree/develop/.claude/skills/handsontable-unit-testing into .opencode/skills/handsontable-unit-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "handsontable-unit-testing", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
handsontable-unit-testing- GitHub stars
- 22k
- Token cost
- ~1.2k tokens
- SKILL.md length
- 415 words
- Files
- 1
- Skills in repo
- 31
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Conventions for Handsontable's Jest unit and TypeScript type tests: where files go, how to run them, mocking limits and when to write an E2E test instead.
- Writing or changing Jest unit tests for Handsontable core, plugins or utilities
- SKILL.md covers Unit vs E2E, Conventions, Run commands and Large datasets, plus 3 more sections
- Calls npm, npx and tsc
- Adding TypeScript type tests for a public API change
What it does
The guide covers unit tests named *.unit.js or *.unit.ts, kept in __tests__ folders beside the source, and TypeScript type tests named *.types.ts. Tests run on Jest with jsdom and the jest-jasmine2 runner, with module aliases that map handsontable and walkontable paths to the source and styles to a mock. The test bootstrap supplies ResizeObserver and IntersectionObserver mocks, and other mocking uses jest.fn and jest.spyOn.
It favors end-to-end tests. Pure logic, utilities and data transformations suit unit tests, while DOM interaction, rendering and browser events go to Playwright tests, and a unit test that needs a mocked module should become an E2E test. Run commands are given for the whole suite and for a targeted path pattern, along with two traps where a run looks green while testing nothing: passing several patterns in one call, and invoking Jest without the task's own environment settings, which reports zero tests.
When your agent uses it
- Writing or changing Jest unit tests for Handsontable core, plugins or utilities
- Adding TypeScript type tests for a public API change
- Deciding whether a case needs a unit test or an E2E test
- Adding coverage for a bug fix or internal refactor
Example prompts
- “Add a unit test for the new data filter helper under its __tests__ folder.”
- “Write a type test for the new plugin option, using real assignments.”
- “My targeted unit run printed green but zero tests ran. What went wrong?”
Requirements
- A checkout of the Handsontable repository
- Node.js with npm
What it can do on your machine
Read from SKILL.md and the folder at commit 68b5e97. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
npmnpxtsc
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm and npx, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Handsontable Unit Testing loads about 1.2k tokens when it runs. Until then it costs about 113 tokens; SKILL.md has 415 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 415 words (~1,214 tokens).
“"E2E" means a new Playwright test in tests/e2e/ (skill handsontable-playwright-e2e). The handsontable() / selectCell() globals are legacy Jasmine helpers, unavailable in unit tests; add no new *.spec.js.”
- name
- handsontable-unit-testing
Files
Just SKILL.md in .claude/skills/handsontable-unit-testing of handsontable/handsontable.
Open the folder on GitHubat commit 68b5e97
Compare with similar skills
Handsontable Unit Testing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Handsontable Unit Testing this skillhandsontable/handsontable | 22k | — | ~1.2k | Automated safety check: Pass | Custom licence | |
| Designing TestsCloudAI-X/claude-workflow-v2 | 1.4k | 1 repos | ~1.5k | Automated safety check: Pass | MIT | |
| Playwright Testingchongdashu/vibejam-starter-pack | 149 | — | ~2.1k | Automated safety check: Pass | None | |
| Playwright Testingchongdashu/vibejam-starter-pack | 149 | — | ~2.2k | Automated safety check: Pass | None | |
| Run Unit TestsAzure/cosmos-explorer | 131 | — | ~638 | Automated safety check: Pass | MIT | |
| Testingradix-ng/primitives | 274 | — | ~3.3k | Automated safety check: Pass | MIT |
Similar skills
Playwright Testing
chongdashu/vibejam-starter-pack
Plan, implement, and debug frontend tests: unit/integration/E2E/visual/a11y.
Playwright Testing
chongdashu/vibejam-starter-pack
Plan, implement, and debug frontend tests: unit/integration/E2E/visual/a11y.
- Official
Run Unit Tests
Azure/cosmos-explorer
Run unit tests for the Cosmos Explorer project. An agent skill from Azure/cosmos-explorer.
Testing
radix-ng/primitives
Test Radix NG primitives across every layer and pick the RIGHT one for a change: Vitest unit (zoneless), jest-axe a11y, Playwright browser regression (apps/visual-regression), SSR…
Web Testing with Playwright and Vitest
withkynam/vibecode-pro-max-kit
Covers web testing from unit to E2E, load, visual, accessibility and security checks, with Playwright, Vitest and k6 guides plus a Playwright setup script.
More from handsontable/handsontable
All 31 skills in this repoHandsontable Playwright E2E Tests
handsontable/handsontable
Guides writing and changing Playwright end-to-end tests for Handsontable using page objects, data-testid hooks and deterministic waits.
Handsontable Angular Wrapper Development
handsontable/handsontable
Guides changes to the @handsontable/angular-wrapper package: the HotTableComponent lifecycle, NgZone performance handling, settings services and the ng-packagr build.
BrowserStack Live Testing
handsontable/handsontable
Opens a live BrowserStack session on a real Android, iOS or desktop browser for a local or public URL, tunneling localhost through Cloudflare when needed.
Handsontable Changelog Entry
handsontable/handsontable
Decides whether a code change needs a changelog entry and creates the JSON file in .changelogs with the right type, framework and user-facing title.
Code Review Graph Navigator
handsontable/handsontable
Queries a pre-built, Tree-sitter-based code graph of the whole monorepo instead of grepping call chains, for exploring, debugging, refactoring or reviewing code.
Handsontable Coordinate Systems
handsontable/handsontable
Explains Handsontable's physical, visual and renderable row and column coordinate spaces and how to convert between them with IndexMapper, for debugging misplaced rows or columns.
Related
Works with
Categories
Questions about Handsontable Unit Testing
What does Handsontable Unit Testing do?
Conventions for Handsontable's Jest unit and TypeScript type tests: where files go, how to run them, mocking limits and when to write an E2E test instead. ts. Tests run on Jest with jsdom and the jest-jasmine2 runner, with module aliases that map handsontable and walkontable paths to the source and styles to a mock.
When should I use Handsontable Unit Testing?
Handsontable Unit Testing fits situations like: writing or changing Jest unit tests for Handsontable core, plugins or utilities; adding TypeScript type tests for a public API change; deciding whether a case needs a unit test or an E2E test; adding coverage for a bug fix or internal refactor.
How do I install Handsontable Unit Testing in Claude Code?
Run `npx skills add handsontable/handsontable --skill handsontable-unit-testing -a claude-code`. Or copy the skill folder (.claude/skills/handsontable-unit-testing in handsontable/handsontable) into .claude/skills/handsontable-unit-testing in your project. Claude Code loads it when a task matches its description.
How do I install Handsontable Unit Testing in Codex?
Run `npx skills add handsontable/handsontable --skill handsontable-unit-testing -a codex`. Or copy the skill folder (.claude/skills/handsontable-unit-testing in handsontable/handsontable) into .agents/skills/handsontable-unit-testing in your project. Codex loads it when a task matches its description.
Can I use Handsontable Unit Testing in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add handsontable/handsontable --skill handsontable-unit-testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/handsontable-unit-testing, .gemini/skills/handsontable-unit-testing, .github/skills/handsontable-unit-testing and .opencode/skills/handsontable-unit-testing in your project.
What does Handsontable Unit Testing need to run?
Going by SKILL.md and its folder, Handsontable Unit Testing needs the command-line tools its instructions call (npm, npx and tsc). Our summary lists: A checkout of the Handsontable repository; Node.js with npm.
Does Handsontable Unit Testing access the network?
SKILL.md contains no URLs. Its commands use npm and npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Handsontable Unit Testing safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Handsontable Unit Testing use?
Handsontable Unit Testing has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Handsontable Unit Testing use?
About 1.2k tokens (SKILL.md is roughly 4.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Handsontable Unit Testing?
Skills that share tags, products or a category with Handsontable Unit Testing: Designing Tests (CloudAI-X/claude-workflow-v2, 1.4k stars), Playwright Testing (chongdashu/vibejam-starter-pack, 149 stars), Playwright Testing (chongdashu/vibejam-starter-pack, 149 stars) and Run Unit Tests (Azure/cosmos-explorer, 131 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Handsontable Unit Testing?
handsontable (a GitHub organization) maintains it in handsontable/handsontable, which has 22,059 GitHub stars. The repository holds 31 skills in this directory. The repository was last updated on October 7, 2026.
Source: handsontable/handsontable on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.