ProvarDx Reporting
This article presents a summary of a substantial ProvarDx upgrade, focusing on the user interface (UI) aspect of two essential features: PDF report generating and email report sending. These enhancements are intended to simplify your experience and better integrate ProvarDx with the ANT interface for a more effortless user journey.
Generate PDF Report
We have added an “Email” tab to the Export Window in the upcoming ProvarDx release. The goal of this update is to make it easier to create and email PDF execution reports. The ProvarDx Email tab will have a layout similar to the ANT interface, which is well-known to many users. To be in line with the ANT design,
Note: The properties.json file will include an entry for email. When no default JSON file is present, the default email option selected will be “Don’t send an Email.”
Depending on the selected email option, the labeling of the checkbox will vary. If “Don’t send an Email” or no email option is chosen, the checkbox label will be “Generate PDF execution report.” If “Email the Test Run report” is selected, the label will change to “Attach PDF execution report.”
The ability to attach zipped HTML reports won’t change because execution will always produce HTML reports regardless of the email options chosen. The user’s choice inside the Email tab will determine how the email and attachment setups behave. These arrays’ settings will adjust dynamically to reflect the user’s preferences.
ProvarDx will now be even more user-friendly and effective in our opinion, enabling you to easily create PDF execution reports. If you have any questions or need further assistance, please don’t hesitate to reach out to our support team.
Email Execution Reports
In the same export window above we have simplified the process of sending execution summary reports via email after your test execution is completed. This feature draws inspiration from the functionality available in ANT, making it easier for you to configure and send emails with PDF and Zip (HTML, JUnit) reports.
Here are the key aspects of this feature:
- “Email” tab to the ProvarDx export window to make configuring email options easier. This user-friendly interface will make it easier to set up email notifications.
- When you open the Email tab, you’ll see that the default setting roughly mimics that of the corresponding window in ANT. This familiarity provides a smooth transition for ANT users.
- The properties.json file in your Provardx project will have a separate section for email configuration. This entry has two arrays: one for email configuration parameters (emailProperties) and one for attachment details (attachmentProperties), allowing you to customise your email settings.
- The behaviour of the email and attachment parameters will dynamically adapt. This means your settings will be adjusted accordingly, giving you complete control over your email reports.
To ensure the successful implementation of this feature, we’ve provided various configuration options:
- Navigate to the Email tab on the export window and choose “Email the Test Report option’ and specify the Email Subject and recipients.
- Select PDF and HTML attachment as needed and export the json.
- The email sent will include the subject specified in the “Email Subject” field.
- The email will be sent to the addresses specified in the Primary, Cc, and Bcc fields, allowing you to reach the right recipients.
- The email sending behavior will align with your selection of PDF and Zip report options, ensuring you only include the attachments you need.
- The PDF included in the email will be generated according to the configuration within the Email window, giving you full control over the report format.
- Users can conveniently configure their email accounts directly using the “Email Configuration” option.
- The “Close” and “Export” functions operate as usual. Upon export, the ProvarDx properties file will contain email, attachment, subject, and recipient configurations, ensuring your settings are saved and ready for use.
This functionality allows Provar users to send full test execution reports for ProvarDx execution via email with ease. It provides flexibility and control over reporting options while being consistent with ANT’s known behaviour. We feel that this addition will streamline your testing process and improve your overall Provar experience.
- 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
- Salesforce Connection Best Practices
- Improve Your Metadata Performance
- 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
- 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