Smoke Tests

Note: This version of RabbitMQ for Pivotal Platform is no longer supported because it has reached the End of General Support phase. To stay up to date with the latest software and security updates, upgrade to a supported version.

RabbitMQ for PCF runs a set of smoke tests during installation to confirm system health.

Smoke Test Steps

The smoke tests perform the following for each available service plan:

  1. Targets the org system and creates a space to run the tests.
  2. Deploys an instance of the CF RabbitMQ Example App to this space
  3. Creates a RabbitMQ service instance and binds it to the CF RabbitMQ Example App
  4. Checks that the CF RabbitMQ Example App can write to and read from the RabbitMQ service instance
  5. Cleans up all deployed application and all its service bindings. Finally, the cf space is deleted.

Note: Smoke tests fail unless you enable global default application security groups (ASGs). You can enable global default ASGs by binding the ASG to the system org without specifying a space. To enable global default ASGs, use cf bind-running-security-group.


If errors occur while the smoke tests run, they are summarized at the end of the errand log output. Detailed logs can be found where the failure occurs.

When encountering an error when running smoke tests, it can be helpful to search the log for other instances of the error summary printed at the end of the tests, for example, Failed to target Cloud Foundry. Lookout for TIP: ... in the logs next to any error output for further troubleshooting hints.

Was this helpful?
What can we do to improve?