Database Operations
Adding a Database Connection Step
For database operations, first, add a connection step to a test case via the Database Browser, click and drag any table or data into your test case and select Open a connection to the Database.
The following DB Connect test step will be created:
Then save the test case.
Updating a Row in the Database
This test step can update columns of an existing row of data using a WHERE clause.
Click on a row in the Database Browser and drop it into the test case. Select the option Update a row in the table.
Then choose the columns for the update. The first column indicates which field to include in the WHERE clause and the second means which areas should be updated on database operations.
The following test step parameters will be added:
Then save the test case.
Inserting a Row in the Database
Click on a table or row of data in the Database Browser and drop it into the test case. (If you use a row of data, the fields will be pre-populated based on the row.)
Select the option Insert a row into the table. Then choose the fields you want to include.
Then save the test case.
Deleting a Row from the Database
This test step can delete a row of data from a table using a WHERE clause.
Click on a row of data from the Database Browser and drag it into the test case.
Select the option Delete a row from the table. Then specify which fields you want to include in the WHERE clause.
The following parameter will be added:
SQL Queries
An SQL Query can be generated using the Database Browser. To do this, drag a table or row into the SQL Editor view:
You can also create a query using the shortcut CTRL + Enter or click on the icon highlighted below:
Read and Assert from the Database Table
In Provar, you can read the data out of a table and also assert its contents in a single test step.
Drag a row from the Database Browser and drop it into the test case. Select the Read and assert row.
Then choose the columns. The first column indicates which field to include in the WHERE clause, the second means which areas should be read, and the third indicates which columns should be asserted.
Read and Assert from the Database Table
Then review and adjust the parameters added to the test case:
Then save the test case.
- 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
- 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
- Provar desktop
- Provar Test Builder
- Refresh and Recompile
- 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
- DevOps
- 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
- CircleCI
- Copado
- Docker
- Flosum
- 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
- 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
- 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
- Troubleshooting
- Browsers
- Configurations and permissions
- Connections
- DevOps
- Error messages
- 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
- Update to Opportunity field validation behaviour
- Licensing, installation and firewalls
- Memory
- Test Builder and test cases
- Release notes