Flakiness analysis
Not every failure is a bug. Tynkr knows the difference.
Most test monitoring tools show you red and green. Tynkr shows you why— by analyzing the root cause of every failure before deciding whether it's real or noise.
How it works
Two scores, one verdict
Every time a test fails, Tynkr runs it through two layers of analysis before surfacing a verdict to your team.
Root cause classification
Tynkr looks at what actually happened — not just that the test failed. Was it a network timeout? A missing element? A 500 error from your backend? Each signal maps to a root cause category.
Flakiness verdict
Based on the root cause, Tynkr assigns one of three verdicts so your team knows exactly what to do next.
auth_logincheckout_flowsearch_resultspassword_resetapi_timeoutSignal detection
What signals Tynkr reads
Tynkr collects and correlates five categories of evidence from every execution before forming a verdict.
Flakiness score
The flakiness score (0–100)
For workflows with 5+ executions, Tynkr calculates a score based on pass rate variance. A test that fails 50% of the time scores highest — that's the definition of flaky. A test that always fails scores low — it's just broken.
Pass rate → flakiness score
Score peaks at 50% pass rate. Drops to near zero when a test consistently passes or consistently fails.
Confidence
Confidence included
Every verdict comes with a confidence level (0–100%) and a plain-English rationale.
“Transport or environment instability appears intermittently”
“Client-side runtime issue usually reproduces consistently”
No black box. You see exactly why Tynkr called it a flake — the evidence is right there alongside the verdict.
Output
The output your team actually uses
Each analyzed execution includes a structured report your team can act on immediately — no digging through raw logs.
- A one-line summary of what happened
- The probable cause and which phase it affected
- Supporting evidence (network trace, console log, step that failed)
- Recommended next steps — specific actions, not generic advice
Stop triaging noise. Focus on what actually broke.
Tynkr classifies every failure automatically. Your team gets verdicts, not just red lights.