HTTP Return Code Assertions
I am evaluating tools for use in our QA/test team.
I have been informed that in SOAP-UI Pro the user is unable to apply ‘preformed’ assertions on the HTTP return codes, (200, 404, etc…), in the UI as such, when exercising methods in a REST web-service.
I am no great expert in this field as yet, but could you tell me:
1. Could this be an issue when running automated scripts (attended and unattended)?
2. Is there an alternate method? i.e. Is there an effective ‘workaround’?
I have done some digging around and I’ve been told that there is a way around this by writing customised Groovy scripts and interrogating the HTTP Header data.
I have been informed that in SOAP-UI Pro the user is unable to apply ‘preformed’ assertions on the HTTP return codes, (200, 404, etc…), in the UI as such, when exercising methods in a REST web-service.
I am no great expert in this field as yet, but could you tell me:
1. Could this be an issue when running automated scripts (attended and unattended)?
2. Is there an alternate method? i.e. Is there an effective ‘workaround’?
I have done some digging around and I’ve been told that there is a way around this by writing customised Groovy scripts and interrogating the HTTP Header data.