Use this test step to create a binding between a queue and an exchange on an AMQP broker. A binding is a rule that the exchange uses to route certain messages to certain queues.
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 settings 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 Properties and Custom AMQP Bind Queue Test Step Properties panels in the Navigator.
Properties
Name | Description |
|---|---|
Name | The test step’s name. |
Description | Text that describes the test step. |
Custom AMQP Bind Queue Test Step Properties
The values on the Custom AMQP Bind Queue Test Step Properties tab are available for other test steps in your project. For instance, you can verify these property values with the Assertion test step, or check them and change the execution flow with the Conditional GoTo test step.
You can load 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 |
|---|---|
queueName | Specifies the name of the queue. NoteCorresponds to the Queue option specified in the test step editor. |
exchangeName | Specifies the name of the exchange. NoteCorresponds to the Exchange option specified in the test step editor. |
routingKey | Specifies the routing key. NoteCorresponds to the Routing key option specified in the test step editor. |
If the test step is run as part of a test case, you can see the test log in the Transaction Log panel.