Gmail Connection in Automation with App Password
From May 2022 onwards, Google has revoked the option for the less secure apps to interact with third-party apps to keep your account secure.
Note: If you are creating a new Gmail connection in Automation, you might face issues due to changes in Gmail security settings. You must create a Gmail connection in Automation with an app password.
Above: Snapshot of Google message for third-party apps.
If you have a test scenario where you are creating a Gmail connection and testing with Automation, then you will need to follow the instructions given below to successfully create a Gmail connection.
Step 1: Sign in to your Gmail account and click Manage your Google Account under the profile icon.
Step 2: Click Security.
- If 2-Step verification is turned-off ; then follow the instructions from Step 3 and enable it first.
- If 2-Step Verification is turned-on; then follow the instructions from Step 9.
Step 3: Under Signing in to Google section, click 2-Step Verification.
Step 4: Click Get Started.
Step 5: Gmail will ask you to enter your Gmail password. Click Next.
Step 6: Enter your phone number and select your preferred option for the verification code. Click Next.
Step 7: You will receive a verification code on the preferred option you selected in Step 6. Enter the code. Click Next.
Step 8: Click TURN ON. You have successfully enabled 2-step verification.
Generate an App Password to access Third party App
Step 9: Follow Step 1 and Step 2 to navigate the Security tab. In the section Signing in to Google, click App passwords.
Step 10: Gmail will ask you to enter your Gmail password. Click Next.
Step 11: Select Other (Custom Name) in the Select app drop-down.
Step 12: Enter the app name as ‘Provar’. Click Generate.
Step 13: Copy the password highlighted in yellow and place it in some secure location, as this will be the password to connect to Provar. Click Done.
Step 14: Open Automation and Add Gmail connection using Password Authentication.
Step 15: Enter the App Password you generated in Step 13 and paste it into the password field. Click Test Connection to check the connection. A message ‘The connection test was successful’ is displayed.
- 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
- 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
- Provar desktop
- Provar Test Builder
- Refresh and Recompile
- Reintroduction of CLI license Check
- 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
- Generate Test Case
- List compare
- Page Object Cleaner
- 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 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
- 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
- Execution Environment Security Configuration
- Provar Jenkins Plugin
- Parallel Execution
- Running Provar on Linux
- Salesforce DX
- Team Foundation Server
- Version control
- Provar Automation trial guide and extensions
- Salesforce Testing
- Adding a Salesforce connection
- Assert Page Error Messages on Add/Edit Product
- Internationalization support
- List and table testing
- Salesforce Release Updates
- Salesforce Lightning Testing
- Salesforce Lightning Web Component (LWC) locator support
- Salesforce console testing
- Visualforce Testing
- Provar Manager
- Best Practices
- Configurations and permissions
- Error messages
- Licensing, installation and firewalls
- Test Builder and test cases
- Release Notes