Details
-
Suggestion
-
Status: New
-
Resolution: Unresolved
-
None
-
None
-
None
-
UI
Description
Description
In Test Execution, customers have different Test Runs assigned to different users. They would like an email notification being automatically sent to the assignee of the next Test Run when the previous Test Run is completed.
User friction
Currently, the next Test Run assignee may not be aware that the previous Test Run has been completed and that it is now their turn to execute their assigned test. This requires manual communication or monitoring of test execution status.
Steps to reproduce (right now) / Actual Result:
- Create multiple test runs in sequence.
- Assign each test run to a different user.
- Complete the first test run.
- Check the next test run and its assignee.
Actual Result:
No automatic email notification is sent to the assignee of the next Test Run when the previous Test Run is completed.
IMPACT
What would improve if solved:
The next assignee would be notified automatically as soon as the previous Test Run is completed. This would make the Test Execution process more seamless and reduce the need for manual coordination.
Impact on stakeholders:
- Know immediately when they need to start their assigned Test Run.
- Less manual follow-up and coordination.
- Helps to maintain a smoother and more predictable Test Execution workflow.
Current workaround:
Teams need to manually inform the next Test Run assignee that the previous Test Run has been completed, or the assignee must regularly check the Test Execution status.
CONTEXT & EXAMPLES:
Concrete example:
A Test Execution consists of three sequential test runs:
- Test Run 1 → assigned to Tester A
- Test Run 2 → assigned to Tester B
- Test Run 3 → assigned to Tester C
Once Tester A completes Test Run 1, Tester B should automatically receive an email informing them that Test Run 2 is ready for execution. Once Tester B completes Test Run 2, Tester C should receive a similar notification.
Workaround risk:
Manual notifications or status checking can lead to delays if the next assignee is not informed promptly. This can interrupt the testing sequence and potentially delay the overall test execution timeline.