Update to Opportunity field validation behaviour
Salesforce frequently makes changes and updates on different Orgs and Objects. In the Spring ‘22 release, there is a change on the Opportunity object. Salesforce has changed its layout for the New Opportunity screen and has changed the page validation message on the Opportunity object. You will notice this change when you create a New Opportunity in Salesforce. Earlier, the page error messages were displayed as messages right above the form. Please refer to the screenshot given below.
Above: Page validation error messages as displayed earlier in the “New Opportunity” screen.
With the change in the Salesforce layout in Spring ‘22, it is now displayed as a pop-up at the bottom of the screen. Please refer to the screenshot below.
Above: Page validation error messages as displayed in the “New Opportunity” screen as on date.
How do I resolve this?
To ensure your legacy test cases continue to work with the new page validation messages on the New Opportunity screen, you might need to update your test cases. Please see the examples given below for more information.
Steps to update the page error assertion on the Opportunity object
The steps to update the page error assertion are explained with the help of examples. As a user, if you come across the page assertion messages, you may have to update your test cases as mentioned below.
In Salesforce, when an error occurs on the New Opportunity screen; the error message is displayed as “Review the following fields” whereas previously the error message was displayed as “Review the errors on this page”.
In the existing test case, on the Test Builder, right-click on the UI Assert test step and click Edit the Test Step.
Above: Editing the UI Assert test step.
An Edit Test Step section in the Test Builder is displayed. In the Expected Page Message section you can see “Review the errors on this page” text; you have to edit this text to “Review the following fields”. Please refer to the screenshot below.
Above: Screenshot displays updating the “Expected Page Message”.
Click Save and execute the test case again. It will be executed successfully.
In Salesforce, if an error occurs on the New Opportunity screen, when required field(s) are missing then it is displayed as a bulleted list as given below:
- Close Date
- Account name
whereas previously it was displayed as “These required fields must be completed: Account Name, Close Date, Opportunity Name, Stage”.
Above: Updating the old error message in the “Expected Page Message” with the new error message.
In your existing test case, on the Test Builder, right-click on the UI Assert test step and then click Edit the Test Step.
An Edit Test Step section in the Test Builder is displayed. In the Expected Page Message section you will see “These required fields must be completed: Account Name, Close Date, Opportunity Name, Stage” text; edit this text to “Close Date”.
So, when this test case is executed, the UI Assert test step will basically check (i.e. search the page message string) from the bulleted field list as listed below, for the “Close Date”.
- Close Date
- Opportunity Name
- Account Name
Above: Updating the “Expected Page Message” with “Close Date”.
Click Save and execute the test case again. It will be executed successfully. Please refer to the screenshot below.
Above: Screenshot displaying the assertion is successful.
Similarly, you can map and assert each of these fields separately i.e. (Opportunity Name, Stage, Account Name).
Where can I learn more?
If you need more information on this issue or if you are experiencing any other unexpected errors, please get in touch with our Customer Success team via the Provar Success Portal or email [email protected].
- 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
- 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
- List compare
- 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
- 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 issue
- 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
- Version 2.8.0 Winter ’23
- Version 2.7.2
- Version 2.7.0 Summer ’22
- Version 2.6.3
- Version 2.6.0 Spring ’22
- Version 2.5.0 Winter ’22
- Version 2.4.1
- Version 2.4.0 Summer ’21
- Version 2.3.1
- Version 2.3.0 Spring ’21
- Version 2.2.1
- Version 2.2.0 Winter ’21
- Version 2.1.1
- Version 2.1.0 Summer ’20
- Version 2.0.5
- Version 2.0.4
- Version 2.0.3 Spring ’20
- Version 1.9.12
- Version 1.9.11