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
Describe the bug
The testRun field triggerResult.grpc does not include the grcp status code and the webApp is defaulting it to 200. This 200 value does not match with the tracetest.response.status attribute in the Tracetest trigger span. The error is visible now because we added the ability to create a TestSpec from the TriggerResponse data. If you try to create a TestSpec from the ResponseData - Status field for a GRPC trigger you will see the mismatch.
To Reproduce
Steps to reproduce the behavior:
Go to a grpc test run, trigger tab.
Hover on the Status field and select Create test spec
Save the spec and validate the result
Expected behavior
The triggerResult.grpc.code field should match the value from the tracetest.response.status attribute in the Tracetest trigger span.
Screenshots
The text was updated successfully, but these errors were encountered:
Describe the bug
The testRun field
triggerResult.grpc
does not include the grcp status code and the webApp is defaulting it to200
. This 200 value does not match with thetracetest.response.status
attribute in theTracetest trigger
span. The error is visible now because we added the ability to create aTestSpec
from theTriggerResponse
data. If you try to create a TestSpec from the ResponseData - Status field for aGRPC
trigger you will see the mismatch.To Reproduce
Steps to reproduce the behavior:
grpc
test run, trigger tab.Status
field and selectCreate test spec
Expected behavior
The
triggerResult.grpc.code
field should match the value from thetracetest.response.status
attribute in theTracetest trigger
span.Screenshots
The text was updated successfully, but these errors were encountered: