Running Provar Tests on Docker using Docker File
Running Provar tests on Docker when you have Docker installed on your machine. Then you can build the image using the Dockerfile. Please refer to the Docker integration help page to submit a form to request this file.
The Dockerfile uses global arguments to specify which version of Provar to target and use in the container, namely PROVAR_DEFAULT_VERSION, and PROVAR_MAJOR_VERSION. The major version represents the first three decimal values of a Provar version (i.e., 1.9.10 and 1.9.11). The default version represents the full Provar version to target (i.e., 1.9.10.02).
You can target any of the following versions (the Dockerfile will always use the most recent Provar ANT files):
- 1.9.10.02
- 1.9.11.05
- 1.9.12.04
- Latest
Docker File
(1) Open a command shell (PowerShell in Windows or Terminal on Mac) and input the following commands.
(2) Download the example Dockerfile to your Provar test project root directory (location of .testproject)
(3) Navigate to your Provar test project root directory (location of .testproject file)
(4) Run the following command to build the Docker container
$ docker build -t <your_tag_name_here> .
(5) Once the build completes, you can run the docker image by running this command:
$ docker run -it -v <location_to_save_reports_locally>:/home/<PROJECT_NAME>/ANT/Results --name provartests <your_tag_name_here>
- -v maps the ANT results folder to your local file system to grant visibility to test reports
- Note you must use /c/path/to/resultsto map files to a Windows host. This command is optional.
- The -d command automatically removes the container after execution. This option will also return control of the terminal immediately and not give test output. This command is optional.
- -it allows for a pseudo-TTY and keeps STDIN open even if not attached. This command is optional.
You should see the following output after executing the commands above:
This will run your Provar tests inside the docker container using the build file that you generated previously. The results/reports will be inside this container and can be copied elsewhere for reporting. They are also mapped to the machine’s local file system via the -v command.
(6) To copy a file from a container to the host, you can use the command:
$ docker cp <containerId>:/file/path/within/container /host/path/target
(7) To find the docker container’s id, you can use the command:
$ docker ps
(Add -a to include exited containers.)
The container’s id is listed in the first column (copy this value).
(8) To copy the results of the test run to your machine, input the following command into another command window (to copy the complete directory, reference the directory itself, no *):
(9) The docker container cannot execute docker commands (natively), so this command must be executed on the host machine.
$ docker cp 48e22cb4076b:/home/ProvarProject/ANT/Results/ C:\users\16156\ProvarDocker\Results\
- Provar Automation
- System Requirements
- Browser and Driver Recommendations
- Installing Provar Automation
- Updating Provar Automation
- Licensing Provar
- Granting Org Permissions to Provar Automation
- Optimizing Org and Connection Metadata Processing in Provar
- Using Provar Automation
- API Testing
- Behavior-Driven Development
- Consolidating Multiple Test Execution Reports
- 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
- Japanese Language Support
- Override Auto-Retry for Test Step
- Mapping and Executing the Lightning Article Editor in Provar
- Managing Test Steps
- Namespace Org Testing
- NitroX
- Provar Automation
- Provar Test Builder
- ProvarDX
- 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
- Provar Manager
- How to Use Provar Manager
- Provar Manager Setup
- Provar Manager Integrations
- Release Management
- Test Management
- Test Operations
- Provar Manager and Provar Automation
- Setting Up a Connection to Provar Manager
- Object Mapping Between Automation and Manager
- How to Upload Test Plans, Test Plan Folders, Test Plan Instances, and Test Cases
- Provar Manager Filters
- Uploading Callable Test Cases in Provar Manager
- Uploading Test Steps in Provar Manager
- How to Know if a File in Automation is Linked in Test Manager
- Test Execution Reporting
- Metadata Coverage with Manager
- Provar Grid
- DevOps
- Introduction to Provar 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
- 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
- Version Control
- Masking Provar Credentials on CI
- Salesforce Testing
- Best Practices
- Salesforce Connection Best Practices
- Improve Your Metadata Performance
- Testing Best Practices
- Automation Planning
- Supported Testing Phases
- Provar Naming Standards
- Test Case Design
- Create records via API
- Avoid using static values
- Abort Unused Test Sessions/Runs
- Avoid Metadata performance issues
- Increase auto-retry waits for steps using a global variable
- Create different page objects for different pages
- The Best Ways to Change Callable Test Case Locations
- Working with the .testProject file and .secrets file
- Best practices for the .provarCaches folder
- Best practices for .pageObject files
- Troubleshooting
- How to Use Keytool Command for Importing Certificates
- Browsers
- Configurations and Permissions
- Connections
- DevOps
- Error Messages
- Provar Manager 3.0 Install Error Resolution
- Provar Manager Test Case Upload Resolution
- Administrator has Blocked Access to Client
- JavascriptException: Javascript Error
- macOS Big Sur Upgrade
- Resolving Failed to Create ChromeDriver Error
- Resolving Jenkins License Missing Error
- Resolving Metadata Timeout Errors
- Test Execution Fails – Firefox Not Installed
- Selenium 4 Upgrade
- Licensing, Installation and Firewalls
- Memory
- Test Builder and Test Cases
- Release Notes