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

'ElementToBeSelected' and 'ElementSelectionStateToBe' have identical behavior #1645

Closed
zyrconium13 opened this issue Feb 16, 2016 · 1 comment
Labels

Comments

@zyrconium13
Copy link

Hi guys,

Maybe it's just me but it seems the expected conditions 'ElementToBeSelected' and 'ElementSelectionStateToBe' seem to have the same behavior. Is this intended? Because if it is it seems rather confusing. It makes the API look like it is offering more functionality, when in fact it is not.

P.S.: I'm concerned with .Net implementation.

Thank you.

@rouke-broersma
Copy link

The documentation seems to be copy pasted and slightly wrong.
ElementToBeSelected calls ElementSelectionStateToBe with value true.
ElementSelectionStateTobe takes a boolean.
So you can use ElementSelectionStateToBe to check if an element is selected or NOT selected, while you can only use ElementTobeSelected to check if a value is selected.

It's basically just a fancy named method wrapper to declare intent in the method name only, and not need the boolean value.

@lock lock bot locked and limited conversation to collaborators Aug 16, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants