Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: add visible, properties, and attributes to waitForElement #412

Merged
merged 1 commit into from
Dec 16, 2022

Conversation

jrandolf
Copy link
Contributor

This PR adds three new properties:

  • attributes - This is a dictionary of strings that will match attributes of an element. This will always be a partial match.
    For example, ”attributes”: {“value”: “125”}.
  • properties - This is a JS record of JSON-serializable attributes that can be used to match an element’s JSON-serializable properties. This will be a sub-tree exact match. For arrays, order matters.
  • visible - This is a boolean value that inverts the match criteria.

@jrandolf jrandolf requested a review from OrKoN December 16, 2022 10:50
test/runner.test.ts Outdated Show resolved Hide resolved
src/Schema.ts Outdated Show resolved Hide resolved
Copy link
Collaborator

@OrKoN OrKoN left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's update the stringify extension and add the benchmark tests in the same PR.

@jrandolf jrandolf changed the title feat: add hidden, properties, and attributes to waitForElement feat: add visible, properties, and attributes to waitForElement Dec 16, 2022
@jrandolf jrandolf force-pushed the assertion branch 3 times, most recently from 1e8ecdc to 9983e5c Compare December 16, 2022 11:11
Copy link

@Shannonj1 Shannonj1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants