Closed blackcatsonly closed 5 months ago
@JGibson2019 Proposed change to allow ScanOptions to limit the scope of the Scan
Please update the documentation (docs/AutomationReference.md
and, for the CLI, the README.md under src/cli
) with your new options.
@DaveTryon @codeofdusk Thanks for reviewing. I believe I've addressed all the comments from the first iteration. Would you please take a second look?
@blackcatsonly Please update the AutomationReference
docs.
@codeofdusk Thanks, missed than one! Updated in latest iteration.
/azp run
/azp run
/azp run
Attention: Patch coverage is 94.23077%
with 3 lines
in your changes are missing coverage. Please review.
Project coverage is 72.21%. Comparing base (
4fc19c3
) to head (aefe4da
). Report is 383 commits behind head on main.:exclamation: Current head aefe4da differs from pull request most recent head 37b41b3. Consider uploading reports for the commit 37b41b3 to get more accurate results
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
/azp run
Thanks @codeofdusk!
Details
Adds:
Motivation
Proposal to address issue #1021
Context
I exposed internals of A11yAutomation to the Integration Tests project so I could find a relevant IUIAutomationElement for testing the ScanOptions' HWND constraint
You could implement this as a "ForWindowHandle()" constraint on the Config, but my external tools use the same scanner repeatedly - it's the individual Scans whose scope needs to be constrained.
Pull request checklist