Email Testing in Automation
Email Setup in Automation
In email testing in Automation, you need first to create an Email Connection in Automation and then subscribe to them in your Test Case. Your Email Connection can use either Gmail or Microsoft Exchange.
Select the Connections tab from the ‘Test Settings’ tab and click the + button to create a new Connection.
Option 1: Adding a Gmail Connection
Select ‘Google’ on New Connection for the Connection type and Google Applications option in the following dropdown. Automation offers two options for making the Gmail Connection: Web-based 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 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.
Please refer to the Gmail Connection in Automation with the App Password page.
Option 2: Adding a Microsoft Exchange Connection
Select Microsoft for Connection type and MS Exchange in the following dropdown on a new connection.
Provar offers three options for making the Microsoft Exchange connection: an Online Exchange Account, Exchange 2007 or later (via EWS), or an 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: MS Exchange Server 2007 or later (via EWS)
- Set Type to Exchange 2007 or later (via EWS) and Enter User Name and Password.
- Select a Host 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.2: 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. Don’t hesitate to contact your Technical support team to enable IMAP4 support if this is not already enabled.
- Set the Type to Older version of Exchange (via IMAP), and enter your Host Name, User Name, and Password.
- Select Test Connection and click OK if successful.
You can see this under the Connections tab once you finish creating your Gmail or MS Exchange connection.
- 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