Nijam

What Nijam is

Nijam is a web and API service for analyzing test reports uploaded by continuous integration workflows. It accepts results from Playwright, pytest, and Vitest, then organizes them into test history, failures, flaky-test rankings, and suite analytics. Nijam is read-only: it ingests test results produced elsewhere and does not execute or rerun tests. Its flakiness scoring considers retries across runs. For Playwright failures, it can display the error, stack trace, failing line, trace, screenshots, and video for each attempt. Analytics cover pass rate, duration, and volume across runs, branches, and spec files. Reporters are available for its three supported frameworks, and uploads can come from GitHub Actions, GitLab CI, Jenkins, CircleCI, Azure Pipelines, or a laptop. Nijam supports Slack run notifications, GitHub pull-request status checks and comments, and GitLab merge-request commit statuses and results notes. MCP-capable clients such as Claude Code, Cursor, and Codex can query history with a read-only key. The Free plan costs $0 forever and includes 1,000 credits per month, up to three members, and seven-day history retention. Pro costs $20 per month and includes 10,000 credits, unlimited members, and 90-day retention.

Who it suits

Nijam suits software teams using Playwright, pytest, or Vitest that want test history, failure details, and flaky-test rankings from CI reports. Its read-only analysis model fits teams that already run tests in their CI workflow and want results surfaced in collaboration tools.

Limits

The Free plan includes 1,000 credits per month, up to three members, and seven-day history retention. Pro costs $20 per month and includes 10,000 credits, unlimited members, and 90-day retention; additional credits cost $0.002 each, or $0.001 at the early-bird rate.

Getting started

1. Visit nijam.dev and choose the Free plan or Pro plan.
2. Set up a reporter for Playwright, pytest, or Vitest.
3. Upload runs from GitHub Actions, GitLab CI, Jenkins, CircleCI, Azure Pipelines, or a laptop.
4. Connect Slack or GitHub or GitLab reporting if those integrations fit your workflow.
5. Use an MCP-capable client with a read-only key to query test history, if desired.

Verdict

Choose Nijam if your team uses Playwright, pytest, or Vitest and wants CI test history, failure analysis, and flaky-test tracking. Look elsewhere if you need a service that executes tests, self-hosted deployment, or formal SOC 2 or ISO 27001 certification.