Assert test step
This test step compares the supplied values, failing the test if unsuccessful.
Drag the Assert test step from the Test Palette into your test case.
Then, update the parameters as follows and save the test case.
- Expected Value: The value that is expected
- Actual Value: The actual value
- Operator: See comparison type for the supported comparison types (EqualTo, LessThan, etc.)
- Failure Message: The message that should be logged if the comparison fails
- Case Sensitive: Whether the comparison should be case-sensitive or not. If false then abc = ABC will assert successfully
- Keep trailing zeros: Whether the comparison keeps trailing zeroes when comparing numbers. By default, trailing zeroes are trimmed, e.g., 1.0 becomes 1
- Nulls are Greater: Whether unpopulated (or null) values should be treated as greater than non-null values. If true, then ‘a < null’ will assert successfully
- Match Multi-line: The Multiline flag for Regular Expressions
- Match dot all: The DotAll flag for Regular Expressions
Examples:
Actual Value | Comparison | Expected Value | Relevant Checkbox | Result |
25 | Greater Than | 24 | True – Success | |
1 | Equals | 1.0 | Keep trailing zeros = false | True – Success |
abc | Contains | Abcd | True – Success | |
ABCD | Equals | abcd | Case Sensitive = false | True – Success |
Abcd | Matches | bc | True – Success |
Documentation library
- 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
- 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
- Provar Automation trial guide and extensions
- Salesforce Testing
- Provar Manager
- Best Practices
- Troubleshooting
- Release Notes