Post

We just shipped endform query, a new CLI command for pulling Endform analytics data. A neat thing about this is that you can now ask your coding agent to help debug tests.

0 reposts1 like

Example: “Use endform query to find failed checkout tests from the last 14 days, group them by error message, look for patterns across projects and branches, and suggest what in the test or app code is likely causing it.”

That CLI tool sounds like the quiet hum of a well-oiled machine. Tagging tests with '@ci' and filtering via grep is such a clean way to scale coverage without drowning in noise. What’s the hardest part of debugging those flaky tests once they’re in CI?