Selenium Protractor Tutorial: Guide With Examples & Tips

Protractor is an end-to-end testing framework developed by Google Developers to support Angular applications. Though it was initially designed for Angular and AngularJS apps, it now supports both Angular and non-Angular applications.

Note: This guide covers Protractor the software testing framework, not the geometry tool for measuring angles. Protractor is also now deprecated - see the status and migration options below before starting a new project.

What Is Protractor in Software Testing?

In software testing, Protractor is an end-to-end test framework built on Node.js and created by Google to test Angular and AngularJS applications in a real browser. It also automates non-Angular sites because it drives browsers through Selenium underneath.

Architecturally, Protractor is a wrapper around WebDriverJS, the JavaScript bindings for Selenium WebDriver. It communicates with browsers through a Selenium Server and layers Angular-aware behavior on top - most notably automatic waiting, which syncs each test step with Angular's rendering so you write fewer manual waits. Here is how the pieces fit together:

• Test runner: Jasmine (default), Mocha, or Cucumber defines and executes the test specs.
• Spec files (spec.js): hold the actual test cases and assertions.
• Config file (conf.js): sets the Selenium address, browser capabilities, and which specs to run.
• WebDriverJS + Selenium Server: translate commands into real browser actions.

Is Protractor Deprecated? Status and Alternatives

Yes. The Angular team announced Protractor's deprecation in April 2021, and Protractor reached end of life on August 31, 2023, per the Angular team's deprecation update. Its GitHub repository was archived in July 2024, so it no longer receives updates or security fixes.

For any new project, start with a maintained framework. Common choices are Playwright, Cypress, WebdriverIO, Puppeteer, and native Selenium WebDriver, all of which the Angular team pointed to as migration paths. TestMu AI runs each of these across 3,000+ browser and OS combinations, so you can move a legacy Protractor suite to a supported framework without losing cross-browser coverage. The getting started with HyperExecute documentation covers orchestrating those runs.

The chapters below still help if you maintain an existing Protractor suite. They cover the everyday tasks - locators, waits, windows, iframes, and debugging - you need to keep it running while you plan a migration.