Closed Thevakumar-Luheerathan closed 7 months ago
Thevakumar-Luheerathan
commented
7 months ago This issue comes when a common global client is mocked differently(same object method is mocked in different ways) across different test functions. When parallel execution is enabled, one mocking behavior of the client is replaced with another mocking behavior. So, there are failures in the test function assertion.
github-actions[bot]
commented
7 months ago This issue is NOT closed with a proper Reason/ label. Make sure to add proper reason label before closing. Please add or leave a comment with the proper reason label now.
- Reason/EngineeringMistake - The issue occurred due to a mistake made in the past.
- Reason/Regression - The issue has introduced a regression.
- Reason/MultipleComponentInteraction - Issue occured due to interactions in multiple components.
- Reason/Complex - Issue occurred due to complex scenario.
- Reason/Invalid - Issue is invalid.
- Reason/Other - None of the above cases.
Description
$subject sample - https://github.com/gayaldassanayake/training-content/tree/parallel-test
Steps to Reproduce
No response
Affected Version(s)
No response
OS, DB, other environment details and versions
No response
Related area
-> Test Framework
Related issue(s) (optional)
No response
Suggested label(s) (optional)
No response
Suggested assignee(s) (optional)
No response