Jobs · 11

Testing and debugging

Catch the break before your users do

Use this when the app is real enough to fail in public. End-to-end tests, error monitoring, and bug reports that carry context back to the code.

Initial editorial estimate. Not a measured benchmark. Edit scores in data/tools.json.

1. 01

   Sentry

   Best for Knowing what broke in production

   Error monitoring. The stack trace from production, with the release.

   • + The SDK drop-in is a known afternoon of work
   • + Stack traces are grouped instead of living in a log hose

   • − It tells you about failures. It does not prevent them
   • − Quota pricing: check site

   7.7

   Freemium

2. 02

   Playwright

   Best for End-to-end tests of a web app

   Microsoft's open-source framework for end-to-end browser tests.

   • + Open source and free
   • + One API for the three major browser engines

   • − End-to-end tests are slower and flakier than unit tests if you write them carelessly
   • − You have to run them somewhere. CI minutes are not free

   7.6

   Free

3. 03

   Jam

   Best for Bug reports that include the evidence

   Bug reports with console, network, and a replay, not a vague screenshot.

   • + The report arrives with context, which is the expensive part
   • + Faster than a screen recording plus a paragraph

   • − It does not replace automated tests or error monitoring
   • − Pricing: check site

   7.4

   Check site

4. 04

   Checkly

   Best for Production checks on a timer

   Monitoring that runs Playwright-style checks against production.

   • + The checks are code, and Playwright is a first-class option
   • + Catches production-only failures CI never sees

   • − Another bill on top of the tests you already run in CI
   • − Pricing: check site

   7.1

   Check site