Above: This diagram provides a high-level overview of how each architecture layer should be configured.
The application layer consists of two major elements:
A workstation running on macOS or Windows with a full Provar installation. We recommend that you always use the latest version of Provar, especially when running your test cases via continuous integration and continuous delivery (CI/CD).
A version control system (VCS) setup to contain your Provar test project(s). This can be Git, SVN, TFS, etc.
Note: To learn more about integrating Provar with your version control system of choice, please refer to Version Control and Devops.
Once you have made your initial check-in to your VCS, the next phase is implementing the environment layer.
The environment layer consists of two major elements:
A full package installation of Copado in your Salesforce org.
A Jenkins server accessible from the internet.
Note: The installation of Copado will not be covered in this guide and must be managed/supported by your Copado representative/consultant.
Once you have this package installed and correct access has been provisioned, you must also setup your Jenkins server to be publicly accessible from the internet. That configuration will be covered in a later section.
The platform layer consists of two major elements:
Your Salesforce org.
Amazon Elastic Compute Cloud (EC2) instance or Azure Virtual Machine (VM).
This guide will be configuring the integration using an Amazon EC2 instance.
Setup for the Azure VM would be similar. More documentation can be found here.
These instances should have at least 8 GB RAM, 50 GB of storage space, and a high-speed internet connection.
Note: In both cases we recommend that you use a Linux distribution as your base since these are generally more secure and have better performance.
- General information
- Licensing Provar
- Provar trial guide and extensions
- Using Provar
- API testing
- Behavior-driven development
- Creating and importing projects
- Creating test cases
- Debugging tests
- Defining a namespace prefix on a connection
- Defining proxy settings
- Environment management
- Exporting test cases
- Exporting test projects
- Managing test steps
- Namespace org testing
- Provar desktop
- Provar Test Builder
- Refresh and Recompile
- Reload Org Cache
- 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
- Test Palette introduction
- Control test steps
- List compare
- Read test step
- String test steps
- UI Test Steps
- Using custom APIs
- Callable tests
- Data-driven testing
- Page objects
- Applications testing
- Database testing
- Document testing
- Email testing
- Mobile testing
- OrchestraCMS Testing
- Salesforce CPQ testing
- ServiceMax testing
- Skuid testing
- Vlocity testing
- Webservices testing
- Introduction to test scheduling
- Apache Ant
- Configuration for sending emails via the Provar Command Line Interface (CLI)
- Continuous integration
- Azure DevOps
- Running a Provar CI task in Azure DevOps
- Configuring the Provar 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
- Circle CI
- GitLab CI
- Travis CI
- Parallel Execution
- Running Provar on Linux
- Salesforce DX
- Team foundation server
- Version control
- Zephyr Cloud and Server (Beta)
- Salesforce testing
- Adding a Salesforce connection
- Assert Page Error Messages on Add/Edit Product
- Internationalization support
- List and table testing
- Salesforce critical updates
- Salesforce Lightning Testing
- Salesforce Lightning Web Component (LWC) locator support
- Service Cloud console testing
- Visualforce Testing
- Testing best practices
- Configurations and permissions
- Error messages
- Licensing, installation and firewalls
- Test Builder and test cases
- Release notes