Collect Selector FAQs

Question 1

How does this skill improve my workflow?

Accepted Answer

It eliminates the manual effort of hunting for IDs in source code. By providing a predictable logic—prioritizing playwrightId first, then data-testid, then text—it reduces test fragility and automatically suggests IDs for components that lack them.

Question 2

When should I use this skill?

Accepted Answer

You should use this skill during the test development phase whenever you need to identify how to target a component. It is especially useful for standardizing tests across teams that use different naming conventions like playwrightId and data-testid.

Question 3

What is the output format of this skill?

Accepted Answer

The skill returns a simple string representing the resolved data-testid value. If no match can be determined, it returns 'undefined-testid', signaling that a manual identifier may be required.

Question 4

What does the Collect Selector skill do?

Accepted Answer

This skill determines the optimal data-testid for UI components based on a specific priority hierarchy. It ensures that Claude uses consistent, reliable selectors when writing or maintaining Playwright and end-to-end test suites.

Question 5

What happens if a component has no existing ID or text?

Accepted Answer

The skill follows a four-tier logic. If no ID or text is found, it will automatically generate a relevant 'playwrightId' for the component to ensure it can be targeted in your automation suite.

Collect Selector

주요 기능

사용 사례

Collect Selector

주요 기능

사용 사례