mocha

Mocha JavaScript test framework. Use for Node.js testing.

7 stars

Best use case

mocha is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Mocha JavaScript test framework. Use for Node.js testing.

Teams using mocha should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/mocha/SKILL.md --create-dirs "https://raw.githubusercontent.com/G1Joshi/Agent-Skills/main/skills/testing/mocha/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/mocha/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How mocha Compares

Feature / AgentmochaStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Mocha JavaScript test framework. Use for Node.js testing.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Mocha

Mocha is a flexible JavaScript test framework. Unlike Jest, it does _not_ come with an assertion library, mocking, or snapshotting built-in. It is a runner that allows you to choose your own tools (usually Chai + Sinon).

## When to Use

- **Flexibility**: You want to pick your assertion library (Chai, Should.js).
- **Node.js Backends**: standard in many Express/NestJS (legacy) setups.
- **Asynchronous Testing**: Historically strong support for async (though standard now).

## Quick Start

```javascript
// npm install --save-dev mocha chai
const assert = require("chai").assert;

describe("Array", function () {
  describe("#indexOf()", function () {
    it("should return -1 when the value is not present", function () {
      assert.equal([1, 2, 3].indexOf(4), -1);
    });
  });
});
```

## Core Concepts

### BDD Interface

`describe` (suite), `it` (test), `before`, `after`, `beforeEach`, `afterEach`.

### Hooks

Mocha allows defining hooks at the root level or inside suites to set up/tear down environments.

### Async support

Use `async/await` in the `it` block callback.

```javascript
it("should save user", async function () {
  const user = new User("tobi");
  await user.save();
});
```

## Best Practices (2025)

**Do**:

- **Use `.only` and `.skip`**: Useful during development to run a single test (`it.only(...)`).
- **Use `nyc` (Istanbul)**: For code coverage (since Mocha doesn't have it built-in).

**Don't**:

- **Don't use arrow functions** (`() => {}`) if you need `this.timeout()` or `this.slow()`. Mocha binds the test context to `this`.

## References

- [Mocha Documentation](https://mochajs.org/)