01 / Technologies / Testing

Detect Jest in any GitHub repo

Jest is a JavaScript testing framework with built-in mocking, snapshots and coverage.

Why show Jest on your README

Showing the test runner tells contributors how to run the suite before they open package.json.

How Jest is detected

Stack Fingerprint reads the repo's full file tree in one GitHub API call and flags Jest when it finds any of these:

  • Files or folders: /^jest\.config/, jest.setup.js, jest.setup.ts
  • Dependencies in package.json: jest

Jest README badge

A static badge you can paste anywhere in Markdown:

Jest badge

Markdown
![Jest](https://img.shields.io/badge/Jest-C21325?style=for-the-badge&logo=jest&logoColor=white)

Or let the repo describe itself

Static badges go stale the moment you swap a dependency. A Stack Fingerprint card is generated from the repo, so Jest (and everything around it) appears or disappears on its own:

Tech stack card for jestjs/jest
jestjs/jest · generated live from the repo
README.md
[![Stack Fingerprint](https://stackfingerprint.vercel.app/api/card?repo=OWNER/REPO)](https://stackfingerprint.vercel.app/?repo=OWNER/REPO)

Replace OWNER/REPO with your repository, or open the builder to pick a theme and layout.