Testing & QA · By reticlehq

Applies red-green TDD to behavior unit tests cannot reach, by stating the expected outcome against the running app with Reticle before writing the feature.

reticlehq/reticle

Sweeps a running web app by clicking every reachable control, then reports dead buttons, console errors, failed requests and mismatches between API data and the screen.

reticlehq/reticle

Finds why a running web app misbehaves when the console is empty and the code looks fine, by reading the click, request, store and console together.

reticlehq/reticle

Drives and verifies Electron or Tauri desktop apps through Reticle, which sees the renderer and the IPC calls that a browser-based testing tool cannot observe.

reticlehq/reticle

Finds out why a passing test suite sits on top of a broken app by comparing what the running app does with what the tests claim, using Reticle.

reticlehq/reticle

Picks up bugs a person flagged by pointing at elements in the running app, each mark carrying the element, their note and the source file and line, then fixes and verifies them.

reticlehq/reticle

Saves a user journey driven through the app as a deterministic regression check that replays with no model and no test code, using Reticle.

reticlehq/reticle

Installs Reticle's dev-only SDK in a running web app and verifies user-facing changes by driving a real flow, returning a verdict with the file and line to fix.

reticlehq/reticle

Check that a form actually rejects bad input: the error message renders, the submit button stays disabled, and no request goes out.

reticlehq/reticle