The NitroX User Interface
When using NitroX, you’ll notice some subtle differences to the standard Test Builder user interface. When authoring a Test Case with Test Builder, NitroX will automatically detect custom Lightning Web Components or Screen Flow components that have matched the mapping criteria when selecting Add to Test Case for an element on the page. You’ll be able to identify if NitroX is being used to map a component by seeing the PageStructure section within Test Builder, which shows the structure of the custom component and in the top right-hand corner, the locator strategy with, say, “NitroX Component”.
Above: Snapshot of Test Builder interface.
Page Structure
The Page Structure section displays the component hierarchy used to locate an element on a web page.
Above: Snapshot of Page Structure.
On selecting each level in the hierarchy, the name and type of the component are displayed and highlighted in blue on the web page.
Above: Snapshot of Filters.
Field Details
The field details section displays the information about the element selected:
- Field Title: the name given to mapping the element; this will be pre-populated if NitroX can identify an appropriate label.
- Adaptive Locator: NitroX Adaptive Locators are Provar’s cutting-edge locator solutions that capture numerous web element attributes and then harness this data to pinpoint and interact with elements on a web page automatically. Toggling off Adaptive Locators provides you with the ability to define the locator using ProvarX explicitly.
- Fields: the element attributes or properties that can be used to locate the element.
- NitroX Type: the type of FACT Component that maps to the element selected on the web page.
Above: Snapshot of Field Details.
Depending on the type of element selected, you may also be presented with a Field Detail section, which has a sub-section called Fields that gives you the ability to inject parameterized values for specific element attributes or properties when locating the element to make the locator more reusable and reduce duplication.
Above: Snapshot of Fields.
This allows you to add a parameter, remove a parameter, set the appropriate operator, and set a value or Provar Expression to locate the element.
Above: Snapshot of Parameters.
Above: Snapshot of Parameters with Provar Expressions.
Interaction Type
The Interaction section displays the interactions available for the type of element selected. The list of available interactions will only display interactions available for the current state of the selected element.
Above: Snapshot of Interaction Type.
Some FACT Components may have a specific interaction and user interface to provide a similar user experience for the selected element. For example, the Lightning Slider would appear with a slider:
Above: Snapshot of Interaction Type.
or provide additional validation for particular fields like dates. Nitrox can extract the relevant information to validate the format of the value provided and mirror the experience of the web page.
To get a deeper understanding of NitroX, we recommend the following UP courses:
- 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
- API Testing
- Behavior-Driven Development
- Consolidating Multiple Test Execution Reports
- 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
- Japanese Language Support
- Override Auto-Retry for Test Step
- Mapping and Executing the Lightning Article Editor in Provar
- Managing Test Steps
- Namespace Org Testing
- NitroX
- Provar Automation
- 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 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
- 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
- Masking Provar Credentials on CI
- Salesforce Testing
- Best Practices
- Improve Your Metadata Performance
- Java 21 Upgrade
- Salesforce Connection Best Practices
- 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