npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

eslint-plugin-aaa-pattern

v0.0.2

Published

ESLint plugin that enforces the Arrange-Act-Assert pattern in test code.

Readme

eslint-plugin-aaa-pattern

Enforce the Arrange-Act-Assert pattern in test code via ESLint.

Install

npm install --save-dev eslint-plugin-aaa-pattern

Usage

Flat config (ESLint v9+)

// eslint.config.js
import aaa from 'eslint-plugin-aaa-pattern'

export default [
  {
    files: ['**/*.test.{js,ts}'],
    plugins: { aaa },
    rules: {
      'aaa/pattern': 'error',
    },
  },
]

Or use the bundled recommended config:

import aaa from 'eslint-plugin-aaa-pattern'

export default [aaa.configs.recommended]

Legacy config (ESLint v8)

// .eslintrc.json
{
  "plugins": ["aaa"],
  "overrides": [
    {
      "files": ["**/*.test.js"],
      "rules": {
        "aaa/pattern": "error"
      }
    }
  ]
}

Rule: aaa/pattern

Checks that every test block contains three marker comments — arrange, act, assert — in that order.

it('adds', () => {
  // arrange
  const a = 1
  const b = 2

  // act
  const sum = a + b

  // assert
  expect(sum).toBe(3)
})

Options

{
  "aaa/pattern": ["error", {
    "labels": {
      "arrange": ["arrange"],
      "act":     ["act"],
      "assert":  ["assert"]
    },
    "testFunctions": ["it", "test"],
    "caseSensitive": false,
    "allowEmptySection": true
  }]
}

| Option | Default | Description | |---|---|---| | labels | { arrange: ["arrange"], act: ["act"], assert: ["assert"] } | Accepted comment text for each section. Any match in the array is accepted. | | testFunctions | ["it", "test"] | Names of test-defining calls to inspect. | | caseSensitive | false | If false, label matching ignores case. | | allowEmptySection | true | If false, report when a section has no statements between its comment and the next. |

Customizing labels

Given / When / Then

{
  "labels": {
    "arrange": ["given"],
    "act":     ["when"],
    "assert":  ["then"]
  }
}

Japanese

Because Japanese phrasing varies (準備 vs 前準備, 検証 vs 確認), the plugin ships no Japanese preset — list the wording your team actually uses:

{
  "labels": {
    "arrange": ["準備", "前準備"],
    "act":     ["実行"],
    "assert":  ["検証", "確認"]
  }
}

Auto-fix

When all three section comments are missing, eslint --fix (or your editor's "fix on save") inserts a // arrange / // act / // assert template at the top of the test block. You then move each comment above the code that belongs to it.

Other cases — one or two sections missing, wrong order, empty section — are reported with explicit hints in the error message but are not auto-fixed, because the correct insertion point depends on the test's intent.

License

MIT