Protractor automation testing framework index.
Protractor is an end-to-end test framework for Angular and AngularJS applications. It runs tests in a real browser interacting with it as a user would.
Protractor is developed by Google Developers to test Angular and AngularJS code. Today, it is used to test non-Angular applications as well. It performs a real-world user-like test against your application in a real browser. It comes under an end-to-end testing framework. As of now, Selenium Protractor has proved to be a popular framework for end-to-end automation for AngularJS.
Let’s talk about what it does:
Protractor is a JavaScript framework, end-to-end test automation framework for Angular and AngularJS applications.
Protractor Selenium provides new locator methods that actually make it easier to find elements in the DOM.
Two files are required to execute Protractor Selenium tests for end-to-end automation: Specs & Config. Go through the link above to understand in a better way.
To carry out extensive, automated cross browser testing, you can't imagine installing thousands of the available browsers on your own workstation. The only way to increase browser usage is through remote execution on the cloud. To execute your automation test scripts across a variety of platforms and browser versions, LambdaTest offers more than 3000 browsers.
We recommend Selenium for end-to-end automation for AngularJS because both are maintained and owned by Google, and they build JavaScript test automation framework to handle AngularJS components in a way that better matches how developers use it.
For scripting, selenium locators are essential since if they're off, your automation scripts won't run. Therefore, in any testing framework, these Selenium locators are the foundation of your Selenium test automation efforts.
To make sure that your Selenium automation tests function as intended, debugging can be an effective option. Check the blog to know more.
If you are not familiar with writing Selenium test automation on Protractor, here is a blog for you to get you understand in depth.
Selenium tests are asynchronous and there are various reasons for a timeout to occur in a Protractor test. Find out how to handle timeouts in this Protractor tutorial.
In this Protractor tutorial, learn how to handle frames or iframes in Selenium with Protractor for automated browser testing.
Handle alerts and popups in Protractor more efficiently. It can be confusing. Here's a simple guide to understand how to handle alerts and popups in Selenium.
Protractor is lincensed under the MIT License
Can we run Cypress tests on Safari browser and mobile devices using LambdaTest?
Using NodeJs, What syntax to use if I saved my LambdaTest automation credentials in my system environment?
I am running automation tests on iOS devices using Protractor Selenium
How to click on an element with JS-Protractor?
How to set value in a text field with JS-Protractor?
We currently use Protractor + LambdaTest + Jenkins to execute our test scripts across all major browsers, including Safari, and on real mobile devices.
With Protractor deprecated since the end of 2022, we are planning to migrate our existing automation suite to Cypress.
Before proceeding, we want to confirm: can Cypress, when integrated with LambdaTest, support test execution on the Safari browser and mobile devices (iOS and Android)?
Our goal is to maintain the same cross-browser and mobile test coverage after migration, eventually running the stack as Cypress + LambdaTest + Jenkins.
Can someone confirm if this setup supports Safari and mobile testing with Cypress?
Any suggestions or limitations would be appreciated.
We made a similar transition from Protractor to Cypress earlier this year, and I can confirm that LambdaTest supports Cypress execution in their cloud grid, but with a caveat: Safari and real mobile devices aren’t supported directly for Cypress tests yet.
Cypress runs inside a Chrome-based browser engine, so for mobile or Safari-specific validation, what we did was simulate mobile viewports in Cypress using cy.viewport()
for responsive layout checks.
But for true device/browser validation (like iOS Safari), we still rely on traditional Selenium-based tests.
We now run a hybrid setup: Cypress + LambdaTest for fast, consistent desktop testing, and use Playwright or Selenium for the few critical flows that absolutely need real mobile/Safari validation.
Hope that helps!
Just went through this exact decision point at my org. While LambdaTest has amazing integration with Cypress, including parallel test execution and CI pipelines, Cypress itself doesn’t support Safari or real mobile browsers natively, that’s a limitation on the Cypress side, not LambdaTest.
Our workaround? We migrated most of our regression tests to Cypress for speed and reliability, but kept a small suite in Selenium for mobile and Safari cross-checks.
That way, we didn’t lose coverage while still gaining Cypress’s developer-friendly features.
LambdaTest handled both frameworks really well, so Jenkins just calls both test sets in sequence. If full mobile + Safari coverage is a must, I’d recommend this dual-framework approach.
tthe exact same stack (Protractor + LambdaTest + Jenkins) and faced this during our migration too.
The short answer is: Cypress can be integrated with LambdaTest, but it’s limited to Chromium-based browsers.
That means no native Safari or real device testing via Cypress for now.
What we did to bridge this gap was use LambdaTest Screenshot and Smart UI testing for Safari and mobile devices. We trigger those from Jenkins after the Cypress run to visually validate layouts.
It’s not perfect for full E2E logic, but it helps catch Safari-specific issues.
Also, worth keeping an eye on updates, LambdaTest is expanding Cypress support constantly, so things might change soon.
Just make sure to plan around Cypress’s inherent browser limitations.
Protractor can be downloaded from it’s GitHub repository - https://github.com/angular/protractor
Run Selenium, Cypress & Appium Tests Online on
3000+ Browsers.
World’s first end to end software testing agent.
React hooks for performing testing
REST API integration testing framework based on cucumber.js
A Gorgeous HTML/CSS Reporter for Mocha.js
Taiko is a Node.js library with a clear and concise API to automate Chromium based browsers. Tests written in Taiko are highly readable and maintainable.
node.js module to run a simple http server for mock service responses.
JMock is a library that supports test-driven development of Java code with mock objects. Hels design and test the interactions between the objects in your programs.
vfsStream is a stream wrapper for a virtual file system that may be helpful in unit tests to mock the real file system. It can be used with any unit test framework, like PHPUnit or SimpleTest.
Run and manage integration tests efficiently using Venom executors and assertions
PHP Mocking Framework
Ocaramba Test Framework was designed in Objectivity to propose a common way how people should create Selenium WebDriver tests.
Perform automation testing with Protractor on LambdaTest, the most powerful, fastest, and secure cloud-based platform to accelerate test execution speed.
Test Now