Skip navigation

In the post Building Cloud Components: Testing we introduced you to the Cloud Component Test Utility.

 

Since there is currently no way to test your component within Eloqua, the purpose of the test utility is to ensure that all of your endpoints are working correctly.  This post will walk you through this process step-by-step.

 

Let's get started...

 

When you first navigate to the tool in your browser, you'll see the following:

Main.png

 

Enter the URL to your provider's service definition in the box at the top, then click Test.

Test.png

To tool will then attempt to parse your JSON.  If your provider is successfully parsed, you'll see your JSON and a list of components in the corresponding sections.

Test_Result.png

 

From the Components list, select the component you wish to test, and click the + (plus) sign.  This will call your createInstance endpoint, therefore creating an instance of your component.

 

If your component instance was successfully created, it will be displayed in the Instances section.

AddNew.png

Next, let's test out the Configure endpoint.  Highlight the newly created component and click the wrench icon.  Your configuration page should open in a pop-up.

Config.png

Configure your component and then close the window.

 

Now it's time to test the Render endpoint.  Click the eye icon at the bottom of the page.

Rendered_Content.png

If all worked correctly, your Snapshot and Rendered Content areas should be populated.

 

The last check is the Remove endpoint.  To test this, click the - (minus) sign.

Delete_or_Submit.png

 

Your component instance should be removed from the window, as well as from your system.

 

Once all of your endpoints have been tested successfully, it's time to Submit your app for approval.  Click the Submit button, and the following form will appear.

 

Submit.png

 

Fill in the information and click Submit.  This will kick off the approval process, and you'll be one step closer to having your component in Eloqua and onto the AppCloud!

 

Some things to keep in mind:

 

  • The test utility does not provide much in the way of error messages, so if you're experiencing issues, I recommend using a utility such as Fiddler to see what is going wrong.
  • If your JSON will not correctly parse, make sure that your content-type is correct (text/json or application/json), and that you are bringing back valid JSON.  Use a tool such as JSONLint to check this.