Test run execution

TestMonitor groups test cases into runs that testers work through case by case. A Beam agent watches an active run, reads each case result as it is recorded, and applies your rule for what counts as a blocking failure. When a case fails against acceptance criteria, the agent opens a linked defect and notes the run it came from. Passing cases move the run toward completion without anyone touching them. Anything the agent cannot classify with confidence, such as an ambiguous partial pass, is left for a human tester to judge and close.

Defect logging

Defects in TestMonitor capture what broke, where, and against which case. Prompted by a failed result or an inbound report, a Beam agent reads the failure details, checks them against your severity rule, and files or edits a defect with the right priority and tags. It links the defect to its originating run so testers keep the trail. Duplicates that clearly match an open defect get a comment instead of a fresh record. Reports that look severe or touch unfamiliar areas are handed to a tester before anything is assigned or closed.

Milestone and coverage tracking

TestMonitor ties test cases to milestones and requirements so teams can see what is covered. A Beam agent reads run progress against a milestone, applies your threshold for readiness, and posts a status note when coverage crosses or falls short of it. It can flag requirements with no passing test attached so gaps show up early. Where release timing or sign-off is involved, the agent alerts the owner rather than declaring a milestone done, leaving that judgment call and any scope questions with a human lead who decides.