You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The test result page for Postman tests shows several inconsistencies:
When an operation is not tested because of no script in the collection, it is marked as timed out
When a test case is a success but the global test is timed out, it is still marked as timed out
When a test case is a failure but the global test is timed out, it is still marked as timed out
When a test request is a success but the global test is timed out, it is still marked as timed out
When a test request is a failure but the global test is timed out, it is still marked as timed out
Expected behavior
Not tested operation because of lack of scripts should be marked as a failure with a clear explanation message
Partial success or failure results (as the operation or at the request level) should appear clearly
Actual behavior
See the bug description above.
How to Reproduce?
Launch a Postman test on an operation for which we have no test scripts in the corresponding collection. To see the partial results inconsistencies, each operation must have several requests.
Describe the bug
The test result page for Postman tests shows several inconsistencies:
Expected behavior
Actual behavior
See the bug description above.
How to Reproduce?
Launch a Postman test on an operation for which we have no test scripts in the corresponding collection. To see the partial results inconsistencies, each operation must have several requests.
Microcks version or git rev
1.9.0 and earlier
Install method (
docker-compose
,helm chart
,operator
,docker-desktop extension
,...)all
Additional information
No response
The text was updated successfully, but these errors were encountered: