TheSunIsLeaking/DorkNet
3
0
Fork 0
mirror of https://github.com/DorkSquadRR/DorkNet.git synced 2026-10-25 15:08:47 -07:00
Code Issues Packages Projects Releases Wiki Activity

fix: a closed issue marks the failing test case Passed

Browse Source 
Closed means fixed. The case that was failing on that bug passes, and reopening
the issue undoes it:

  closed + Failed -> Passed
  open   + Passed -> Failed

Replaces the previous closed -> NotYetTested, which sent the case back for
another run instead of recording the outcome.

The guard that matters is unchanged: only those two states are the
reconciler's to move, so a case a tester has Claimed — or one nobody has run
yet — is never rewritten underneath them.
This commit is contained in:
Alexa
2026-07-28 17:16:44 +03:00
parent 7ce106ed1b
commit 0af23c26b1
3 changed files with 28 additions and 30 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/admin.md
+7 -8
View File
@@ -222,15 +222,14 @@ issue number is only read from a URL matching the GitHub issue shape.
| Issue | Case status | Result |
| --- | --- | --- |
| Closed | Failed | → NotYetTested |
| Open | NotYetTested | → Failed |
| anything | Claimed / Passed | untouched |
| Closed | Failed | → Passed |
| Open | Passed | → Failed |
| anything | Claimed / NotYetTested | untouched |
A closed issue does **not** mark the case Passed: closing is a developer's claim
that the fix landed, not a tester's observation that the case passes, so it goes
back in the queue for another run. And only those two states are the
reconciler's to move — a case a tester has Claimed, or marked Passed after
verifying the fix, is never dragged back underneath them.
Closed means fixed: the case that was failing on that bug now passes, and
reopening the issue undoes it. Only those two states are the reconciler's to
move — a case a tester has Claimed, or one nobody has run yet, is never
rewritten underneath them.
## Build And Deploy