A workflow test needs evidence of both inclusion and exclusion. Check the ticket that satisfies every required condition, a nearby ticket that misses one, and an unrelated edit that should not widen the population. Already-closed tickets do not enter the ordinary trigger cycle. Use persisted fields and the rule-attributed audit to decide whether execution occurred. A rule name in a configuration list is not proof that it affected a request.
Start with the required population and inspect the resulting saved fields. The first task supplies the steps; later tasks change the source conditions and ask you to preserve a control record. The workspace executes a disclosed subset of ticket rules locally and never sends a notification to an operational account.
Worked example: trigger acceptance tests.