Test Case Management

PractiTest stores test cases, steps, and their organization across a project. An agent reads the cases relevant to a release on a trigger, applies your rule, and, for example, assembles a run set or updates a case's status after review. It writes the change back where permissions allow and notifies the QA lead. Cases with unclear steps, or ones the agent is not cleared to modify, are left for a person, so the definition of what gets tested stays under the team's control rather than shifting through an automated edit.

Test Run Execution

Test runs in PractiTest record each case's result as passed, failed, or blocked. An agent reads run progress on a schedule, applies your rule, and updates statuses or opens follow-up tasks as results land. It notifies owners when a run stalls or a critical case fails. Runs with many failures at once, or results that contradict a recent pass, are escalated to a QA engineer rather than accepted automatically, so a person confirms whether the product broke or the test itself needs attention before anything is reported.

Defect & Issue Linking

PractiTest ties failed tests to defects so problems stay traceable. An agent reads a failure, applies your rule, and, for instance, links it to an existing defect or records the details for a new one. It updates the linked items and notifies the owner. Failures that could map to more than one defect, or ones touching an area you have marked sensitive, are handed to a person instead of linked automatically, so the connection between a broken test and its cause is one a human has confirmed rather than assumed.