Github-action-jest-flaky-test-analyzer
Identifies and diagnoses flaky Jest tests with actionable fixes and coverage recommendations
Platform availability
Available on 0 of 10 platforms
- Unraid (not listed)
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm (not listed)
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
33/100 Low
- Maintained
- 57last commit 180 days ago
- Popular
- 00 GitHub stars
- Easy to install
- 250 install platforms, install notes, Docker image
- Light to run
- No data
Based on 3 of 4 factors.
- GitHub stars
- 0
- Open issues
- 0
- Last commit
- 2026-05-24
- Activity
- stale
Checked 16 days ago - source: GitHub (SethTBoyer/flaky-test-analyzer)
Resources & Compatibility
Requirements not published yet.
Checked 23 days ago - source: Docker Hub image tags and published docs
First-install notes
- Install Jest and ts-jest first Use your package manager (the program that adds packages to your project, like npm or Bun) to install jest, typescript, ts-jest, and @types/jest as dev dependencies (packages needed only for running tests), so Jest can run TypeScript tests and the analyzer has results to inspect. source
- Tell Jest to use the TypeScript preset In your Jest config (your project's test settings file), include a TypeScript preset from ts-jest, such as createDefaultPreset or createJsWithTsPreset. This tells Jest how to translate TypeScript files, which avoids confusing “syntax” errors before your tests even run. source
- If you use path aliases, add tsconfig-paths If your TypeScript config uses path aliases (short import names instead of long folder paths), import tsconfig-paths/register in Jest’s global setup and teardown files, which are small files that run before and after all tests. That makes Jest resolve the same alias paths your app uses, so tests do not fail with “module not found”. source
Fetched 53 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
Do I need Jest and ts-jest installed in my project to get results the analyzer can inspect?
Yes, install Jest, TypeScript, ts-jest, and @types/jest as dev dependencies so Jest can run TypeScript tests and the analyzer has results to inspect.
Which Jest preset should I configure for TypeScript tests?
Include a TypeScript preset from ts-jest in your Jest config, such as createDefaultPreset or createJsWithTsPreset, so Jest translates TypeScript files before tests run.
What extra Jest setup is needed when my TypeScript project uses path aliases?
Add tsconfig-paths/register in Jest's global setup and teardown files so Jest resolves the same alias paths your app uses instead of failing with module not found errors.
Answers sourced from kulshekhar.github.io, kulshekhar.github.io, kulshekhar.github.io
Community
- Is there a way to reproduce a flaky test in jest? - Stack Overflow (forum)
- Help with Jest tests passing locally but not in Github Actions - Reddit (reddit)
Collected 48 days ago - public community threads