AssertIQ

Static test intelligence and report cards for JavaScript and TypeScript test suites.

npx @mov2day/assertiq
npx @mov2day/assertiq --html
npx @mov2day/assertiq --badge

AssertIQ parses test files only. It does not execute tests or need project-specific config.

CLI

--dir <path>          Path to scan. Default: .
--ignore <glob>      Glob pattern to exclude. Repeatable.
--html               Write assertiq-report.html.
--badge              Write assertiq-badge.svg.
--json               Print machine-readable JSON.
--fail-below <grade> Exit 1 below A, B, C, D, or F.

GitHub Action

Use the latest major tag to auto-pick future patch/minor updates in that major line. Current major line is v0, so use mov2day/assertiq@v0.

name: Test Intelligence
on:
  pull_request:
  push:
    branches:
      - main
permissions:
  contents: write
  pull-requests: read
  issues: write

jobs:
  assertiq:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
        with:
          fetch-depth: 0
      - uses: mov2day/assertiq@v0
        with:
          fail-below: C
          post-comment: ${{ github.event_name == 'pull_request' && github.event.pull_request.head.repo.fork == false }}
          track-history: ${{ github.event_name == 'push' && github.ref == 'refs/heads/main' }}
      - uses: actions/setup-node@v4
        with:
          node-version: 22
      - name: Update badge on main
        if: github.event_name == 'push' && github.ref == 'refs/heads/main'
        run: npx @mov2day/assertiq --badge
      - name: Commit badge
        if: github.event_name == 'push' && github.ref == 'refs/heads/main'
        run: |
          git config user.name "github-actions[bot]"
          git config user.email "github-actions[bot]@users.noreply.github.com"
          git add assertiq-badge.svg assertiq-history.json
          git diff --cached --quiet || git commit -m "chore(ci): update AssertIQ badge and history"
          git push

post-comment needs issues: write. On pull_request runs from forks (and Dependabot PRs), GITHUB_TOKEN is usually read-only, so comment posting may be skipped. Keep post-comment conditional as above, or use a hardened pull_request_target comment-only workflow. track-history writes assertiq-history.json only on push to main when enabled.

When v1 is released, switch mov2day/assertiq@v0 to mov2day/assertiq@v1 to track the latest v1.x.

Release

Pushes to main can auto bump patch version, publish to npm with trusted publishing, and create GitHub release through .github/workflows/release.yml. Trusted publishing handles auth through OIDC, so no long-lived npm token is needed.

Badge

The workflow above writes assertiq-badge.svg on main.

![AssertIQ](./assertiq-badge.svg)

Trend History

When track-history is enabled in GitHub Action, AssertIQ appends a snapshot to assertiq-history.json (capped at last 90 entries). Reports show score movement and trend sparkline from this file.

Dimensions

AssertIQ scores Assertion Quality, Flakiness Risk, Isolation Risk, Naming Clarity, Coverage Balance, and Dead Test Risk. Findings are static risk signals, not proof that a test is broken.