What you need
- At least one captured element
- Access to the project you want to manage
Find the right element fast
- Use search for text, selectors, or URL fragments.
- Filter by tags, stability score, or last activity.
- Sort by recency or stability to prioritize triage.
Understand element health
Each element includes stability data and context you can use to judge reliability.- Review the stability score and risk factors.
- Inspect alternative selectors and fallbacks.
- Check the capture source and environment.
Keep metadata clean
Consistent metadata makes the library useful at scale.- Apply standardized tags (feature, team, release).
- Add short notes with reproduction context.
- Assign ownership when a fix is needed.
Share and collaborate
- Share the element link in tickets or Slack.
- Attach elements to step replays or bug reports.
- Use comments to log investigation notes.
Export and automate
- Copy selectors for Playwright or Cypress tests.
- Export code snippets for QA automation.
- Validate selector stability before committing tests.
Best practices
- Review stability weekly for high-traffic features.
- Consolidate duplicates to keep the library clean.
- Archive elements that are no longer relevant.
Troubleshooting
- If a selector breaks, check the latest capture.
- If search is slow, narrow filters or reduce scope.