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
There are two tests/requests: A (in the screenshot below it is Token Apigee) calls an OAuth token endpoint to generate a bearer token, B (Ping Apigee Bearer in the screenshot) references A and uses the returned access_token for another call to a different endpoint. When invoking test B from command line, if A causes an exception (in my case, it's due to a proxy not being specified, but I suspect it would be for any other reason), the test results still show as one test as successful:
With the first test failing and the second not being run at all (that's what I think), there should be 2 failures:
And it looks like the VSCode extension has the same issue: if an exception occurs during pre-request or request, the test is marked as successful.
The text was updated successfully, but these errors were encountered:
ENVIRONMENT
SCENARIO
There are two tests/requests: A (in the screenshot below it is
Token Apigee
) calls an OAuth token endpoint to generate a bearer token, B (Ping Apigee Bearer
in the screenshot) references A and uses the returnedaccess_token
for another call to a different endpoint. When invoking test B from command line, if A causes an exception (in my case, it's due to a proxy not being specified, but I suspect it would be for any other reason), the test results still show as one test as successful:With the first test failing and the second not being run at all (that's what I think), there should be 2 failures:
And it looks like the VSCode extension has the same issue: if an exception occurs during pre-request or request, the test is marked as successful.
The text was updated successfully, but these errors were encountered: