feat: add priorityAttribute support for element identification #51
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR addresses an issue where elements were not being optimally identified for testing and automation workflows. It introduces support for a configurable
priorityAttribute(defaulting todata-testid), allowing Agentation to generate more robust and reliable selectors.Changes
priorityAttribute.priorityAttributeprop to Agentation (default:"data-testid").data-testidattributes to demo elements in the example app for immediate verification.How to Test
cd _package-export/example && npm run devhttp://localhost:3000[data-testid="..."]instead of generic classes or tags.