Test-Requests are created from standard requests using their "Add to Testcase" action, either from the request-nodes popup menu och from the request-editors corresponding toolbar button. They extend requests with the possibility to add any number of "Assertions" that will be applied to the response received when submitting the request.
Test-Requests are submitted either manually through their editors submit actions or when running the TestCase containing the request. The requests response is validated against a requests assertions and the requests icon changes to reflect the result of the validations; green=all validations ok, red=some validation(s) failed. A grey background icon indicates that the request has not yet been submitted for validation, a white background indicates that the TestRequest lacks assertions
The following actions are available from the test-request nodes' right-button menu:
|
![]() |
The "Details" tab shown in the bottom-left shows the following values when a TestRequest node is selected in
the navigation tree
|
![]() |
Double-clicking a TestRequest in either the navigator or the TestCase Editor Pane opens the requests editor which is more-or-less a copy of the standard request-editor with the following exception:
All other editing/submittal/validation functionality is the same as in the request editor
The Assertions tab lists the assertions that have been configured for the TestRequest. Double-clicking an assertion in the list opens that assertions' configuration dialog (if available). Any number of assertions can be added, often it may be relevant to add the same type of assertion multiple times with different configurations.
A colored circle next to the assertion indicates the status of the assertion in regard to the last received response; red=assertion failed together with error message(s), green=assertion ok, grey=assertion has not been performed.
The following actions are available from the assertion lists right-button menu:
|
![]() |
The Request Log tab simply shows a history of submit/response times and response-sizes for the TestRequest. This can come in handy if you want to manually compare response times or sizes over time. |
![]() |