Product Instrumentation
As we undertake the continual improvement of our application we will soon be auto-enabling a feature to capture additional information about your use of our products to improve and deliver more benefits to our customers:
- Proactive issue identification and collation of common customer issues to automatically calculate incident priority
- Remote resolution of test failures due to product issues
- Reduce the frequency and size of local Automation installation
- Deliver product improvements by understanding the most frequently used features and how they are used.
- Deliver additional product features on demand, and access to pilot or beta features without new product installation
In order to continue delivering these benefits, we have started to capture the following data from release v2.10.2. You can disable the data collection via a feature flag. The data we will be collecting, in addition to the data we collect today for license enforcement, is limited to the following new items:
If you are concerned about this change and wish to speak to us regarding the data collection and usage please contact us so we can discuss further. We will also be holding a Q&A Webinar and Office Hour for you to raise any concerns you may have. In the meantime, see below some potential questions and answers:
Will Provar be increasing the data you collect in the future?
Yes, it’s possible we will want to gather additional data about your use of our products, but we will communicate this in advance and consult with our customers before doing so with time to review the changes before they are enforced.
Are you collecting any PII data?
No, we are not collecting additional PII data. Note that users’ external IP Address data is already collected by us for licensing purposes. Depending on your specific InfoSec policy IP this could be deemed PII but is required to validate access. We handle this data according to our own InfoSec policy and ISO27001 certification, the same way as we hold your contact details in our own CRM. We cannot link individual contact details with an IP address or hostname.
Are you collecting any of my company data from my test cases?
No, we’re only collecting use of our product data. The only exception will be system-generated unique identifiers to help us identify the order of execution and compare different test runs against one another. None of your test steps names, data values, connection names, encryption keys or screenshots are captured unless you choose to share them with us for support purposes.
Can we disable the collection of this data?
Yes, you can disable collection of this data via a feature flag. It can be disabled via the feature flag com.provar.analytics.logging.enabled=false which can be added in the provar.properties file. This way it ‘sticky’ and does not require you to change it after upgrading to a new release or project.
Does this feature flag sit in the Provar.ini file?
Yes, currently this feature is controlled by the Provar.ini and provar.properties file. If the feature flag is not present or is set to true, the functionality will remain ON. The flag value needs to be ‘false’ to disable it.
Will this slow down my test case execution?
No, we have designed this to run asynchronously and not to retry sending data. If our data collector is unavailable and cannot be reached there is no impact to you.
Can I get access to the data you are collecting?
Yes, under data protection rules for your geographic region we will share any data collected while retained on request within the local rules for responding to requests, but only for your license keys and after proof of identity plus approval from your commercial stakeholder.
How long will you hold this data for and where is it stored?
We are updating our InfoSec policies and will make them available to explain how long we hold this data and the purpose we use it for. In general, we will be aggregating data on a rolling basis and archiving individual records within 180 days, or less.
We are holding this data in our own AWS infrastructure and access is limited to authorized Provar employees.
- Home
- 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
- Understanding Provar’s Use of AI Service for Test Automation
- Provar Automation
- Creating a New Test Project
- Import Test Project from a File
- Import Test Project from a Remote Repository
- Import Test Project from Local Repository
- Commit a Local Test Project to Source Control
- Salesforce API Testing
- Behavior-Driven Development
- Consolidating Multiple Test Execution Reports
- Creating Test Cases
- Custom Table Mapping
- Functions
- Debugging Tests
- Defining a Namespace Prefix on a Connection
- Defining Proxy Settings
- Environment Management
- Exporting Test Projects
- Exporting Test Cases into a PDF
- Japanese Language Support
- Override Auto-Retry for Test Step
- Customize Browser Driver Location
- Mapping and Executing the Lightning Article Editor in Provar
- Managing Test Steps
- Namespace Org Testing
- NitroX
- 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 – Chrome Headless
- 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
- Database Testing
- Document Testing
- Email Testing
- Email Testing in Automation
- Email Testing Examples
- Gmail Connection in Automation with App Password
- App Configuration for Microsoft Connection in MS Portal for OAuth 2.0
- OAuth 2.0 Microsoft Exchange Email Connection
- Support for Existing MS OAuth Email Connection
- OAuth 2.0 MS Graph Email Connection
- Create a Connection for Office 365 GCC High
- Mobile Testing
- OrchestraCMS Testing
- Salesforce CPQ Testing
- ServiceMax Testing
- Skuid Testing
- Vlocity API Testing
- Webservices Testing
- DevOps with V2
- 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
- Salesforce Testing
- Recommended Practices
- Salesforce API Access Control Security Update – Impact on Provar Connections
- Salesforce Connection Best Practices
- Improve Your Metadata Performance
- Java 21 Upgrade
- 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
- Testing Best Practices
- Troubleshooting with V2
- How to Use Keytool Command for Importing Certificates
- Browsers
- Configurations and Permissions
- Add Permissions to Edit Provar.ini File
- Configure Provar UI in High Resolution
- Enable Prompt to Choose Workspace
- Increase System Memory for Provar
- Refresh Org Cache Manually
- Show Hidden Provar Files on Mac
- Java Version Mismatch Error
- Unable to create test cases, test suites, etc… from the Test Project Navigation sidebar
- Connections
- DevOps with V2
- Error Messages
- Provar Manager 3.0 Install Error Resolution
- Provar Manager Test Case Upload Resolution
- Administrator has Blocked Access to Client
- JavascriptException: Javascript Error
- 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 and Installation
- Memory
- Test Builder
- Release Notes