QA Arsenal
Tally
Jalaran Tally tracks a test cycle as it runs — what has been executed, what passed, what is blocked — so you can answer "where are we" without counting rows.
Who Tally is for
For whoever has to report cycle status to someone who wants a number. If your current answer to "how is testing going" involves a spreadsheet and a moment of dread, Tally is that spreadsheet with the arithmetic done.
What Tally does
Tally holds a QA cycle as phases with cases underneath, and keeps a running count of what has been executed and how it went. Pass, fail and blocked are tracked separately, because a blocked case is not a failed one and reporting them together hides the reason a cycle is stuck. It can post a reflection summary to a Discord channel when you want the team to see progress without asking. There is no AI in Tally at all — it is bookkeeping, and bookkeeping should be exact.
- Phase-and-case structure across a full cycle
- Pass, fail and blocked tracked as distinct states
- Running execution and coverage totals
- Optional Discord reflection posts
How Tally works
Set up the cycle
Phases with cases underneath, matching how the cycle is actually structured.
Record outcomes as you go
Pass, fail and blocked are tracked separately, because they mean different things to whoever reads the report.
Read the running totals
Execution progress and coverage across the whole cycle, computed rather than tallied by hand.
Post a reflection
Optionally push a summary to a Discord channel so status arrives without anyone having to ask for it.
What Tally does not do
Tally has no AI in it, deliberately — it is a counter, and a counter that estimates is broken. It does not execute tests, integrate with a CI pipeline, or import results from another test management system, so cases and outcomes are entered here. Discord is the only outbound integration, and it is off unless a webhook is configured.
Common questions
Does Tally use AI?
No, and that is deliberate. It is pure bookkeeping — counts, states and totals. Anywhere a number appears it was computed from what you recorded, never estimated.
Why are blocked and failed separate?
Because they mean different things. A blocked case tells you something is in the way; a failed one tells you something is broken. Collapsing them into a single red number hides the reason a cycle is stuck.
Can it pull results from my CI pipeline?
No. There is no CI integration or importer — outcomes are recorded here. The only outbound integration is an optional Discord post.
Works well with
Explore the workspace
Jalaran is one workspace of 85 modules. Browse the rest of the arsenal: