Docker Continuous Integration
Do you use Docker Continuous Integration to package up code more efficiently during your development lifecycle?
Good news! You can use Provar to test those containers to deploy new releases more quickly.
The following describes how to set up Provar to run tests in a Docker container and how to troubleshoot common issues with setup. These steps can be applied to any machine that has a Docker installation.
Note: This setup assumes that you already have an existing Provar installation in your local environment and have Provar tests currently built.
It’s also worth noting that this setup (besides generating a build.xml file) could also be performed on a machine that does not have Provar installed. In this case, however, it is recommended that you generate a build.xml file first and have access to the git repository where the Provar files are checked in.
For this particular guide, a Windows 10 machine is used as an example, with Provar installed locally and a project already created.
Let’s get started!
Prerequisites in Docker Continuous Integration
- A machine with an installation of Provar (if you are generating a new build.xml)
- Provar ANT zip files.
- A Provar project with at least one test case.
- (Optional) Version Control System already set up.
- (Optional) Continuous Integration Tool set up with VCS.
Guide to Installing Docker
For the installation of Docker, please refer to their website documentation. Depending on the target OS, you can follow these links to install Docker:
Requesting a Docker File
To request the Docker file, please log in to the Provar Community and click View/Raise Case to submit your request, and a consultant will contact you shortly.
- 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