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
To continue delivering these benefits, we may start to capture the following data from our next Provar Automation Release (v2.10.2 onwards) by default and will communicate this in advance. You will have the option to disable the collection of this data. The data we will be collecting, in addition to the data we collect today for license enforcement, is limited to the following new items:
Please note that while currently disabled, this feature is already available to use today. We are limiting this to a closed internal pilot with this Automation v2.10.1 release. You can choose to individually opt into this pilot programme by contacting your Provar Success Manager.
If you are concerned about this change and wish to speak to us before this feature is enabled by default in our Winter ‘24 Release on August 25th 2023 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 the collection of this data via a feature flag.
Does this feature flag sit in the Provar.ini file?
Yes, currently this feature is controlled by the Provar.ini file. If the feature flag is not present, or is set to disabled, then no data is sent. Before releasing to general availability we will make sure this setting can be disabled at a Project level so that you do not need to keep switching it off with every Provar release. We are open to discussion if this should also be overridable at an Environment level.
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 in Product, Engineering, and Customer Service teams to perform their duties as needed.
- General information
- Licensing Provar
- Provar trial guide and extensions
- Using Provar
- API testing
- Behavior-driven development
- Creating and importing projects
- Creating test cases
- Custom table mapping
- 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
- Provar desktop
- Provar Test Builder
- Refresh and Recompile
- Reload Org Cache
- 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
- Test Palette introduction
- Control test steps
- Generate Test Case
- List compare
- Page Object Cleaner
- Read test step
- String test steps
- UI Test Steps
- Using custom APIs
- Callable tests
- Data-driven testing
- Page objects
- Block locator strategies
- Introduction to XPaths
- Creating an XPath
- Label locator strategies
- Maintaining page objects
- Mapping non-Salesforce fields
- Page object operations
- Refresh and reselect field locators in Test Builder
- Using Java method annotations for custom objects
- Applications testing
- Database testing
- Document testing
- Email testing
- Mobile testing
- OrchestraCMS Testing
- Guide in Salesforce CPQ Testing in Provar
- Guide in ServiceMax Testing
- Skuid Testing
- Vlocity API Testing
- Webservices testing
- Introduction to test scheduling
- Apache Ant
- Configuration for Sending Emails via the Provar Command Line Interface
- Continuous integration
- AutoRABIT Salesforce DevOps in Provar Test
- Azure DevOps
- Running a Provar CI Task in Azure DevOps Pipelines
- Configuring the Provar 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
- Gearset DevOps CI/CD
- GitHub Actions
- Integrating GitHub Actions CI to Run Provar 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
- Execution Environment Security Configuration
- Provar Jenkins Plugin
- Parallel Execution
- Running Provar on Linux
- Salesforce DX
- Team foundation server
- Version control
- Salesforce testing
- Adding a Salesforce connection
- Assert Page Error Messages on Add/Edit Product
- Dynamic Forms
- Internationalization support
- List and table testing
- Salesforce Release Updates
- Salesforce Lightning Testing
- Salesforce Lightning Web Component (LWC) locator support
- Salesforce console testing
- Visualforce Testing
- Performance Best Practices
- Testing best practices
- Configurations and permissions
- Error messages
- Administrator has blocked access to client
- 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
- Update to Opportunity field validation behaviour
- Licensing, installation and firewalls
- Test Builder and test cases
- Release notes