Valid HTTP code assertion doesn't provide what is expected and what is actual

[vi]

In readyapi when i use Valid HTTP code assertion, when its failed due to mismatch with the response code why don't it gives you what is expected and what is actual.

For example: if i am expecting a return code of 201 and its returning 200, readyapi gives me the following responses

"Response status code 200 is not acceptable list of status codes"

but if they provide with actual and expected , it will be easy to understand.

"Response status code  is :200 , doesn't match with the expected "201"

[nmrao]

If the default functionality is not what you are looking for, you can write script assertion for the same and display your customized message.

[vi]

Thats pain, i recommend smartbear to have  expected and actual displayed in the test result.

[rajs2020]

@sonya_m - Can the OP's expectation be made a feature? It seems like a minor change, but I'm not sure.

[sonya_m · Accepted solution]

nmrao thank you for your reply!

@rajs2020 @vi the Product Team would need to consider this, please create a feature request here.