OrchestraCMS Testing

OrchestraCMS by Stantive is a content management system (CMS) built on Salesforce.

OrchestraCMS has is a multi-frame UI with complex and variant side panels and tabs. These elements can be difficult for traditional automation tools to identify and locate reliably. With Provar, metadata integration to Salesforce gives an easier way to identify and map UI elements, making OrchestraCMS API testing easier to set up and simpler to maintain.

Guide in OrchestraCMS API Testing with Provar


Provar downloads object metadata and stores it locally, so that this information available in metadata while identifying fields. This provides visibility of the data and allows testers to create and modify test data.

Using Provar’s Org Browser, test data can be created quickly via the Create API. This is ideal for creating seed data for a deterministic test case.

OrchestraCMS API testing data can be created quickly via the Create API of Provar's Org browser

OrchestraCMS UI Testing


Provar has a robust method for mapping OrchestraCMS UI fields, using a special By Orchestra CMS Label locator option. Various examples are given below to illustrate its use.

Testing OrchestraCMS Text Fields


OrchestraCMS text fields are recognized using a By Orchestra CMS Label locator, along with the Visualforce page on which the field is configured:

screenshot of OrchestraCMS API testing text fields

OrchestraCMS Frames


Provar’s Test Builder recognizes and manages the Orchestra page frames automatically:

OrchestraCMS Frames is recognized in Provar test builder

OrchestraCMS Tabs


Provar offers a simple way to manage tabs that gets mapped by default.

In addition, Provar’s field locators easily determine the field type. The example below shows a Link Text field type being located automatically. All the tester need to is click Add and Do to include this step in the Test Case:

sample of OrchestraCMS Tabs

Non-Orchestra Tabs


Provar recognizes non-Orchestra tabs automatically and categorizes them as Not an Orchestra tab.

Provar also provides alternative locator types, such as By ID, XPath and others:

Orchestra Buttons


Provar determines tab types and field types automatically. The example below shows a non-Orchestra tab where a Finish button is located By Label as a Button value type:

an example of a non-Orchestra tab where a Finish button is located By Label as a Button value type in OrchestraCMS API testing

Tab Switching


Provar accommodates switching between tabs and for activities happening in different locations. This is done by simply defining the Tab Name and the Interaction Type to be executed:

Provar accommodates switching between OrchestraCMS tabs and for activities happening in different locations

CK Rich Text Editor


Finally, Provar provides support for OrchestraCMS’s frame-embedded CK editor, with Set and Assert interaction types.

OrchestraCMS’s frame-embedded CK editor

Interested to know more about OrchestraCMS testing with Provar? Get in touch today for a full demo.

Review Provar on G2
Documentation library

Other available resources

Looking for something different?

We use cookies to better understand how our website is used so we can tailor content for you. For more information about the different cookies we use please take a look at our Privacy Policy.

Scroll to Top