Google Autologin - TestProject Documentation

TestProject Documentation

Platform Addons Blog Forum

Search…

Welcome to TestProject!

Getting Started

Register and Collaborate

Installation and Setup

Create Your First Test

Why TestProject

Why Should You Use TestProject

What Makes TestProject Unique

Using AI to Improve Testing

TestProject Agents

What is a TestProject Agent?

How Does an Agent fit into the Ecosystem?

Hybrid Cloud and Offline Mode

TestProject Agent in Docker

TestProject Agent on Kubernetes

TestProject Agent CLI

Silent Deployment

Unregistered/Offline Agent

Smart Test Recorder

Create a Test Step

Finding and Using Elements

Available Actions

Available Validations

Step output validations

Using Data Driven Tests and Jobs in TestProject

Schedule and Run Tests

Manage TestProject Agents

Create and Schedule Jobs

Parallel Execution

Reports

Introduction to Reports in TestProject

Types of Plots in TestProject Reports

Individual Run Reports

Get Test Reports via API

Deleting old reports

TestProject Addons

What is an Addon?

Installing Community Addons from the store

Using Addons in the TestProject Recorder

Creating an Addon

Available Addons

Open Source SDK

Using OpenSDK within CI/CD

Using OpenSDK with BDD

Legacy SDK (v1)

Integrations

qTest Integration

BrowserStack Integration

Genymotion Desktop Integration

Jenkins Integration

TeamCity Integration

Sauce Labs Integration

Setting up Email Notification

Slack Integration

CircleCI Integration

GitHub Integration

TestProject API

Getting Started With Using the TestProject API

Articles

Tips And Tricks

Execution Speed & Adaptive Wait

Mobile Scripts Python OpenSDK

Using Page object model and Page Factory with TestProject

Troubleshooting

How to Deal with Dynamic Elements

Troubleshooting Android Device Connection Issues

Organizing and Managing Test Data

Using Parameters Effectively

Element Management

Best Practices for Element Locators

Expanding UI Automation Capabilities with Javascript

Creating automation building blocks with TestProject

Using TestProject with iFrames

How to Execute Tests from Outside the Test Recorder

Create Tests with Random Data

Performing Operations only on Visible Elements

Deploy new APK/IPA with TestProject APIs

Image Comparison in TestProject

Calling REST APIs in a Test

Scrolling to an Element

Window Management in TestProject

Using Natural Language Commands to Run a Test

Setting up Safari for Automation

Setting Up Internet Explorer for Automation

Google Autologin

Send Keys Key List

Troubleshooting DevToolsActivePort file doesn't exists

How To Record a Web Test for a Mobile Browser

Running a Web Test on a Mobile Device

Finding Device UDID

Downgrading Xcode to v12.4 and Below

Supported Environments

Releases

Contact us

Powered By GitBook

Google Autologin

Motivation
Selenium opens the browser in incognito mode. However, for some test scenarios, we would like to login to Google account. Instead of doing it as part of the test flow or running it as a setup method we can do it automatically.
How to do this with TestProject?
1.Chrome keeps the profile locally in
C:\Users\{username}\AppData\Local\Google\Chrome\User Data.
We need to go to the parent folder (Chrome) and do one of the following options:
Create a copy of the User Data folder, let’s call it Test User Data.
Create a new Chrome profile and set the required actions in it, and then
copy this profile (will probably appear as Person 2) to the Test User Data folder instead of the default user (change the name).
Why are we creating this new folder? If any instance of Chrome browser is open while we are trying to create a new WebDriver instance the operation will fail with
an error
InvalidArgumentException: Message: invalid argument: user data directory
is already in use, please specify a unique value for --user-data-dir
argument, or don't use --user-data-dir
So, to avoid closing the browser every time we run a test (which is quite
impossible when we are using TestProject) we use a copy of the profile.
3. Now we want to use the new profile
In TestProject platform create a job and add your test to it. Now click on
the Set Driver Desired Capabilities icon
And add
{
  "goog:chromeOptions": {
    "args": [
      "user-data-dir=C:/Users/dorbe/AppData/Local/Google/Chrome/User Data",
      "profile-directory=Profile 2"
    ]
  }
}
If you are using the SDK just add options (Java code)
ChromeOptions options = new ChromeOptions();
options.addArguments("--user-data-dir=PATH_TO/Test User Data", "profile-directory=Profile 2");
You can see the current profile you are using by navigating to chrome://version inside your Chromr browser.
​

Setting Up Internet Explorer for Automation

Send Keys Key List

Last modified 1yr ago

Copy link