Setting Up Provar Grid
Prerequisites
- Provar Grid Connection Details provided by Provar, these include …
- Provar Grid Username
- Provar Grid API Key
- A valid Provar Automation license key
Provar Grid Configuration
- Login to Provar Manager.
- Once in Provar Manager, select ‘Provar Manager Setup’.
- You will see a tab to enter ‘Provar Grid Details’
- Make a note of the following details from your onboarding email. If you cannot find these, please contact your sales executive.
- Provar Grid Username
- Provar Grid API Key
- Provar Automation Key
* These details must be valid to execute the tests
- Enter the details in the ‘Provar Grid Username,’ ‘Provar Grid API Key’ and ‘Provar Automation License key’ fields respectively.
- Provar Grid is now ready to run tests.
Repository Connection
- In Provar Manager, from the menu options, select VCS (Version control system)
- Create a new record
- Enter a name; this can be anything you like, but we recommend it is something descriptive.
- Select a platform, i.e., GitHub, Bitbucket or Azure DevOps
- Save the new record
- The new record will display with a connection assistant containing the fields necessary to establish a connection. Note: These differ depending on the VCS provider of choice.
- Enter details in the applicable connection assistant fields.
- The connection will be established if valid, and a message will let you know this is the case.
Repository Import
- From the VCS record, select the drop-down menu in the ‘Repository’ section and choose ‘Import.’
- The subsequent screen will show all of the available repositories.
- Those already imported are denoted with a tick,
- and those available for import are denoted with a +.
- From the import screen, select the repository you want to import and click ‘Import.’
Note: To keep the list concise, the initial list only populates with Private repositories. If you want to import a public repository, use the search function to find the desired one.
Branch Import & Configuration
- From the Repository record, in the ‘Branches’ section, select the drop-down and choose ‘Import.’
- The subsequent screen will show all of the available branches in that repository.
- Those already imported are denoted with a tick,
- and those available for import are denoted with a +.
- Select the branches you want to import from the import screen and click ‘Import.’
To learn more about Provar Grid, take the course at the University of Provar.
Documentation library
- 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 Automation
- 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
- Provar Manager
- Provar Manager Setup and User Guide
- Installing Provar Manager
- Configuring Provar Manager
- How to Use Provar Manager
- Managing Your Testing Life Cycle
- Provar Manager Test Execution
- Test Executions and Defect Management
- Provar Manager Test Coverage
- How to Integrate Provar Manager
- 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
- Provar Manager Plugins
- Uploading Existing Manual Test Cases to Provar Manager with DataLoader.Io
- Provar Grid
- 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
- Salesforce Testing
- Best Practices
- Troubleshooting
- Release Notes