Use this test step to simulate the actions of an AMQP consumer. The test step connects to an AMQP broker and fetches a message from a queue.
Note
To use the test step, you must have the AMQP Support Plugin installed. You can install it on the Integrations tab.
To use this test step, you need ReadyAPI Test Licenses. If you do not have it, you can request it on our website or start a trial.
You can modify the setting of the test step in its editor:
 |
Use the Create AMQP Connection and Edit AMQP Connection dialogs to configure connections used by the test step. Both dialogs have the same set of options.
Note
ReadyAPI stores AMQP connections at the project level. This means that a connection defined for one test step can be used for all the test steps in other test cases and test suites of the project.
Connection name
You can also change the test step behavior by using the step properties on the AMQPReceiveTestStep Properties and Custom AMQP Receive Test Step Properties tabs.
AMQPReceiveTestStep Properties
Name | Description |
|---|---|
Name | The test step’s name. |
Description | Text that describes the test step. |
Custom AMQP Receive Test Step Properties
The values on the Custom AMQP Receive Test Step Properties tab are available to other test steps in your project. For instance, you can verify these property values with the Assertion test step, or you can check them and change the execution flow with the Conditional GoTo test step.
You can load the values of custom properties from a file or save them to a file. To learn more, see About Properties.
This tab contains the following properties that provide access to the request and response data:
Name | Description |
|---|---|
ackMessage | Specifies whether ReadyAPI will inform the broker that the message has been received. Possible values: , . NoteCorresponds to the Acknowledge option specified in the test step editor. |
queueName | Specifies the name of the queue from which a message will be fetched. NoteCorresponds to the Queue option specified in the test step editor. |
timeout | A timeout for the test step, in milliseconds. If no message is received within the specified time period, the test step execution will be aborted and the test step will fail. If this property is 0, it is ignored. NoteCorresponds to the Timeout (ms) option specified in the test step editor. |
messageBody | The body of the fetched message represented as a byte array. NoteThis property is read-only. |
messageBodyAsString | The body of the fetched message represented as a string. NoteThis property is read-only. |
If the test step is run as part of a test case, you can see the test log in the Transaction Log panel.