Reintroduction of CLI license Check
We will be enforcing the license check for CLI executions. It is highly recommended that all users ensure they have a valid license for any CLI execution.
To ensure a seamless experience, we advise all users to test the CLI license validation. This will allow you to proactively address potential challenges in your local or server environment before we enforce the mandatory license check in future releases. Find more information here.
FAQs
1. What is a CLI license check?
Similar to GUI, Provar checks for the license at the start of command line execution (ANT/ProvarDx)
2. How to enable this feature to try?
Users must enable this feature flag using com.provar.licensecheck.cli=true in the provar.properties file. To set the feature flag, follow the instructions here.
3. What is the change, and how has it been working so far?
In case of an invalid or no license, Provar was allocating a temporary license and the warning to execute the Provar test cases using the command line. With this change, Provar is stopping to allocate a temporary license in case of an invalid or No license.
4. What do I need to do?
Users must use a valid license to execute the script via the command line (ANT/ProvarDx).
5. How can I ensure my setup is correct
Users can enable the CLI license check flag and dry run the execution on his/her local and server machines to ensure smooth execution. And make changes if there are any challenges. You can also contact our Success team to rectify the errors.
6. What could be the possible reasons for failure
The following reasons could cause execution failure
- The user has no license
- The user has an invalid or expired license
- The user license is already in use
- The license server is not whitelisted in the firewall or proxy server
7. What If I have a valid CLI execution license configured?
No action is needed. You are good with your setup.
- 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
- Provar Manager
- 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