Test Data Generation
Last Modified:
Requirements
A Salesforce OAuth connection (either Web Flow or JWT Flow) must be set up in the project.
Steps to Use
You can access this feature in Provar Automation
- Create a New Test Case using the OAuth Connection.
- Click on the Test Palette to access the Generate Test Data API located under the ProvarAI section.
- Drag and drop the API from the palette into the test case. The input parameters will then appear on the screen.
4. Select the OAuth Connection, the object for which the data will be generated, and the number of rows.
5. Users can select the fields from the “Configure the Test Step parameters” option.
6. A pop-up screen will appear, allowing you to select the fields you want to insert. After making your selections, click OK. If no fields are selected, then data will be generated for required fields by default.
NOTE: This dialog box shows all available fields from the fetched metadata. Some of these fields may not be visible in the UI. When selecting fields, be sure to pick only those visible in your UI.
7. You should be able to see the fields you selected in the Test Step parameters. Note: the fields can be left blank. If any value is entered, it will be ignored.
8. Run the test case. A test data file in .csv
format will be generated within a few minutes. The file name will be displayed in the test runner logs.
9. To view the generated file, navigate to the Templates folder in the Navigator section. Right-click on the Templates folder and select Refresh.
10. Now, you will be able to see the generated files. Two files have been generated since two steps were added in the test case:
- One file contains only the required fields (where the user did not select any fields).
- The other file contains the selected fields.
You can refer to the file names in the test runner logs section for each test step.
11. This file can be used with the Apex Bulk API to upload bulk data to Salesforce. Since the file path is stored in the result variable, users can access it at runtime. First, generate the data, then use the result variable with the Apex Bulk API for data upload.
Note: This is an AI-powered feature, and the generated data may be incorrect in 5-10% of the cases.
- By default, 10 rows of data will be generated if the user does not specify the number of rows.
- A maximum of 1,000 rows can currently be generated.
- If no fields are selected, data will be generated for the mandatory fields of the object.
- The generated file will be stored in the Result Variable, with the file path set to
templates\filename.csv
.
The AI feature in Provar is disabled by default. You can enable or disable it using the -Dcom.provar.automation.ai.services.enabled
flag by setting its value to either true
or false
. This flag can be configured in the Provar INI file or passed as an ANT argument for CI executions.
How to Configure the Flag in the Provar INI File:
For Windows:
- Navigate to the Provar installation folder:
C:\Program Files\Provar
- Locate and open the
provar.ini
file using a text editor. - Add the following entry to the file:arduinoCopy code
-Dcom.provar.automation.ai.services.enabled=true
(Replacetrue
withfalse
to disable the feature.) - Save and close the file.
For MacOS:
- Navigate to the Provar application in the Applications folder.
- Right-click on the Provar application and select Show Package Contents.
- Open the
Contents
folder, then locate theprovar.ini
file inside theEclipse
folder. - Open the
provar.ini
file using a text editor. - Add the following entry to the file:arduinoCopy code
-Dcom.provar.automation.ai.services.enabled=true
(Replacetrue
withfalse
to disable the feature.) - Save and close the file.
Example :
If you experience any issues editing the provar.ini file, refer to this article.
- 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
- 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
- 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 Cases into a PDF
- Exporting Test Projects
- 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 Data Generation
- 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
- 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
- Salesforce Testing
- Recommended Practices
- 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
- Troubleshooting
- How to Use Keytool Command for Importing Certificates
- Installing Provar After Upgrading to macOS Catalina
- 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