-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Feature/lambdatest grid #5260
Feature/lambdatest grid #5260
Conversation
googlebot
commented
Jun 14, 2019
Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
📝 Please visit https://cla.developers.google.com/ to sign.
Once you've signed (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.
What to do if you already signed the CLA
Individual signers
- It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.
Corporate signers
- Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
- The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
- The email used to register you as an authorized contributor must also be attached to your GitHub account.
i️ Googlers: Go here for more info.
1 similar comment
googlebot
commented
Jun 14, 2019
Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
📝 Please visit https://cla.developers.google.com/ to sign.
Once you've signed (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.
What to do if you already signed the CLA
Individual signers
- It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.
Corporate signers
- Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
- The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
- The email used to register you as an authorized contributor must also be attached to your GitHub account.
i️ Googlers: Go here for more info.
I signed it!
I signed it!
2 similar comments
kanhaiya15
commented
Jul 24, 2019
I signed it!
kanhaiya15
commented
Jul 25, 2019
I signed it!
googlebot
commented
Feb 6, 2020
All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter.
We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only @googlebot I consent. in this pull request.
Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the cla label to yes (if enabled on your project).
i️ Googlers: Go here for more info.
1 similar comment
googlebot
commented
Feb 6, 2020
All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter.
We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only @googlebot I consent. in this pull request.
Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the cla label to yes (if enabled on your project).
i️ Googlers: Go here for more info.
kanhaiya15
commented
Feb 6, 2020
I signed it!
Uh oh!
There was an error while loading. Please reload this page.
https://www.LambdaTest.com
PR to add LambdaTest support in Protractor
Description
Add LambdaTest integration support in Protractor. LambdaTest provides a distributed selenium grid which helps you to perform testing on a wide range of browsers on 4+ windows platform and 6+ mac platform.
Motivation and Context
Protractor is a great end to end testing framework and LambdaTest is an amazing cloud browser provider with awesome selenium support. The alliance between the two obviously seems natural. This feature will provide tight integration within Protractor to perform selenium based testing on a wide range of browsers on the cloud which will complement the already existing great tooling and the ecosystem provided by Protractor.
In addition to that, many of our customers are already using Protractor and want test on LambdaTest platform from within the framework
How Has This Been Tested?
Types of changes
Checklist:
This change follows the natural way of adding integration support for a 3rd party testing infrastructure provider.