Email testing
Setup
In order to test emails, you need to first create an Email Connection in Provar and then subscribe to them in your Test Case. Your Email Connection can use either Gmail or Microsoft Exchange.
From ‘Test Settings’ tab, select the Connections tab and click on the + button to create a new Connection.
Option 1: Adding a Gmail Connection
On New Connection, select ‘Google’ for Connection type and Google Applications option in the next dropdown. Provar offers two options for making the Gmail Connection, Web-based Authentication or Password Authentication.
Option 1.1: Gmail Web-based Authentication
- Enter User and select ‘Web-based Authentication’.
- Click ‘Authorise’.
- When the Gmail window opens, enter your Gmail credentials and authorize the connection.
- Check that the rest of the details are populated automatically.
- Select ‘Test Connection’ and click ‘OK’ if successful.
Option 1.2: Gmail Password Authentication
- Enter User, select ‘Web-based Authentication’ and enter Password.
- Select ‘Test Connection’ and click ‘OK’ if successful.
Option 2: Adding a Microsoft Exchange Connection
On new connection, select Microsoft for Connection type and MS Exchange in the next dropdown.
Provar offers three options for making the Microsoft Exchange connection, Online Exchange Account, Exchange 2007 or later (via EWS) or Older version of Exchange (via IMAP). Select the option relevant to your company’s Microsoft Exchange implementation and follow the instructions for your chosen option.
Option 2.1: Microsoft Online Exchange Account
- Enter User Name and Password, then select Online Exchange Account.
- Select Test Connection and click OK if successful.
Option 2.2: MS Exchange Server 2007 or later (includes 2010, 2013 and 2016)
- Enter User Name and Password, then select Exchange 2007 or later (via EWS).
- Select an option between ‘Auto Discover Host Name’ or ‘Use supplied Host Name’. If you chose Use supplied Host Name, enter the Host Name manually.
- Select Test Connection and click OK if successful.
Option 2.3: Older versions of MS Exchange server via IMAP4 protocol (includes 2000, 2003)
To use this option you will require IMAP4 support to be enabled in your Exchange server. Please contact your Technical support team to enable IMAP4 support if this is not already enabled.
- Enter User Name, Password, select Older version of Exchange (via IMAP) and enter Host Name.
- Select Test Connection and click OK if successful.
Once your Gmail or MS Exchange connection is created, you will be able to see this under the Connections tab.
- 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
- 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 (CLI)
- Continuous integration
- AutoRABIT
- Azure DevOps
- Running a Provar CI task in Azure DevOps
- 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
- GitHub Actions
- Running a Provar CI task in GitHub Actions
- 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 CI
- Travis CI
- Jenkins
- Execution Environment Security Configuration
- Parallel Execution
- Running Provar on Linux
- Reporting
- Salesforce DX
- Git
- Team foundation server
- Version control
- Zephyr Cloud and Server
- 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 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
- Memory
- Settings
- Test Builder and test cases
- Release notes
- 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