OrchestraCMS Testing
OrchestraCMS by Stantive is a content management system (CMS) built on Salesforce.
OrchestraCMS has a multi-frame UI with complex and variant side panels and tabs. These elements can be complex 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 maintain.
Guide in OrchestraCMS API Testing with Provar
Provar downloads object metadata and stores it locally to make this information available in metadata while identifying fields. This provides data visibility and allows testers to create and modify test data.
Using Provar’s Org Browser, creating test data is quick via the Create API. This is ideal for creating seed data for a deterministic test case.
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
Recognizing OrchestraCMS text fields using a By Orchestra CMS Label locator, along with the Visualforce page on which the field is set:
OrchestraCMS Frames
Provar’s Test Builder recognizes and manages the Orchestra page frames automatically:
OrchestraCMS Tabs
Provar offers a simple way to manage and map tabs by default.
In addition, Provar’s field locators easily determine the field type. The example below shows a Link Text field type that it locates automatically. All the tester needs to do is click Add and Do to include this step in the Test Case:
Non-Orchestra Tabs
Provar recognizes non-Orchestra tabs automatically and categorizes them as Not an Orchestra tabs.
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 Label locates a Finish button as a Button value type:
Tab Switching
Provar accommodates switching between tabs and activities happening in different locations. This is done by simply defining the Tab Name and executing the Interaction Type:
CK Rich Text Editor
Finally, Provar supports OrchestraCMS’s frame-embedded CK editor with Set and Assert interaction types.
Interested to know more about OrchestraCMS testing with Provar? Get in touch today for a full demo.
- Provar Automation
- Installing Provar Automation
- Updating Provar Automation
- Using Provar Automation
- API testing
- Behavior-driven development
- Creating and importing projects
- Creating test cases
- Custom table mapping
- Functions
- Debugging tests
- Defining a namespace prefix on a connection
- Defining proxy settings
- Environment management
- Exporting test cases into a PDF
- Exporting test projects
- Override auto-retry for Test Step
- Managing test steps
- Namespace org testing
- NitroX
- Provar desktop
- Provar Test Builder
- Refresh and Recompile
- Reintroduction of CLI license Check
- Reload Org Cache
- Reporting
- Running tests
- Searching Provar with find usages
- Secrets management and encryption
- Setup and teardown test cases
- Tags and Service Level Agreements (SLAs)
- Test cycles
- Test plans
- Testing browser options
- Tooltip testing
- Using the Test Palette
- Using custom APIs
- Callable tests
- Data-driven testing
- Page objects
- Block locator strategies
- Introduction to XPaths
- Creating an XPath
- JavaScript locator support
- Label locator strategies
- Maintaining page objects
- Mapping non-Salesforce fields
- Page object operations
- ProvarX™
- Refresh and reselect field locators in Test Builder
- Using Java method annotations for custom objects
- Applications testing
- DevOps
- Introduction to test scheduling
- Apache Ant
- Configuration for Sending Emails via the Automation Command Line Interface
- Continuous integration
- AutoRABIT Salesforce DevOps in Provar Test
- Azure DevOps
- Running a Provar CI Task in Azure DevOps Pipelines
- Configuring the Automation secrets password in Microsoft Azure Pipelines
- Parallel Execution in Microsoft Azure Pipelines Using Multiple build.xml Files
- Parallel Execution in Microsoft Azure Pipelines using Targets
- Parallel execution in Microsoft Azure Pipelines using Test Plans
- Bitbucket Pipelines
- CircleCI
- Copado
- Docker
- Flosum
- Gearset DevOps CI/CD
- GitHub Actions
- Integrating GitHub Actions CI to Run Automation CI Task
- Remote Trigger in GitHub Actions
- Parameterization using Environment Variables in GitHub Actions
- Parallel Execution in GitHub Actions using Multiple build.xml Files
- Parallel Execution in GitHub Actions using Targets
- Parallel Execution in GitHub Actions using Test Plan
- Parallel Execution in GitHub Actions using Job Matrix
- GitLab Continuous Integration
- Travis CI
- Jenkins
- Execution Environment Security Configuration
- Provar Jenkins Plugin
- Parallel Execution
- Running Provar on Linux
- Reporting
- Salesforce DX
- Git
- Team Foundation Server
- Version control
- Provar Automation trial guide and extensions
- Salesforce Testing
- Provar Manager
- Best Practices
- Troubleshooting
- Release Notes