Testing / PractiTest Interview Questions
Explain the execution flow when a tester runs a Test Set and logs a failed result?
sequenceDiagram
participant T as Tester
participant TS as Test Set
participant I as Issue
participant R as Requirement
T->>TS: Opens Test Set and selects Test Instance
T->>TS: Executes steps, marks result
T->>TS: Marks Test Instance as failed
T->>I: Presses Fail and Issue
I->>I: Issue created and linked to Test Instance
I->>R: Requirement status recalculated
- The tester opens a Test Set and selects a specific Test Instance to run
- They work through the test's steps, recording pass/fail for each as they go
- If a step doesn't behave as expected, the tester marks the Test Instance as failed
- Pressing Fail & Issue creates a new Issue automatically linked to that Test Instance
- The Requirement linked to that test, if any, has its status recalculated, moving to FAILED since a linked test just failed
- The new issue is now visible in the Issues module, whether it stays native to PractiTest or is synced to an external tracker
Because each of these steps happens as part of the same execution flow, a single failed test click produces a fully linked chain, from a specific test step, to an issue, to an updated requirement status, without any separate manual bookkeeping.
What triggers the creation of a linked issue in this flow?
What happens to the linked Requirement's status after the failure?
More Related questions...
