locator-parity

Automate AngularJS and React locator parity testing across zip codes and viewports.

Updated May 15, 2026
One-click install
npx skills add https://github.com/Pear-Commerce/pear-ai-skills --skill locator-parity
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: locator-parity
Source: https://github.com/Pear-Commerce/pear-ai-skills/tree/main/skills/locator-parity
Command: npx skills add https://github.com/Pear-Commerce/pear-ai-skills --skill locator-parity

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually comparing legacy AngularJS and new React product locators for functional and visual parity is slow, inconsistent, and easy to miss edge cases across different offers, zip codes, and device viewports.

Core Features & Use Cases

  • Automated Parity Testing: Runs end-to-end comparisons of AngularJS and React product locators for a given vendor offer ID, testing interactions, UI elements, and store data.
  • Cross-Viewport Validation: Tests across 5 US zip codes and both desktop (1280x800) and mobile (390x844) viewports to catch responsive design issues.
  • Divergence Classification: Automatically flags new parity issues while ignoring known accepted divergences (like map pin style and geocoding order differences) and generates a screenshot-backed readiness report. E-commerce teams migrating their product locator from AngularJS to React can use this skill to quickly validate the new locator is production-ready for a specific vendor offer.

Quick Start

Use the locator-parity skill to run a full parity test for offer ID 1740607387970560 and get a report confirming if the React locator is ready for that vendor.

Frequently Asked Questions about locator-parity

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate AngularJS to React UI parity testing for an e-commerce product locator?

Cross-viewport validation tests the product locator across 5 US zip codes using both desktop (1280x800) and mobile (390x844) viewports to catch responsive design issues during the AngularJS to React migration.

How does divergence classification handle known differences during locator parity testing?

Divergence classification automatically flags new parity issues while filtering out known accepted divergences, such as map pin style and geocoding order differences, ensuring the readiness report only shows actionable errors.

Can I use automated browser testing to validate a product locator migration for a specific vendor offer?

Automated browser testing validates the product locator migration by running a full parity test for a given vendor offer ID, confirming if the React locator is production-ready for that specific vendor's offer.

What are the limitations of automated parity testing for AngularJS and React product locators?

Limitations include ignoring known accepted divergences like map pin style and geocoding order differences, and restricting cross-viewport validation to 5 US zip codes with desktop (1280x800) and mobile (390x844) screen sizes.