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

TextCheck#FULL_TEXT is still not the default property #2674

Open
nikitakovaliov92 opened this issue Mar 6, 2024 · 1 comment
Open

TextCheck#FULL_TEXT is still not the default property #2674

nikitakovaliov92 opened this issue Mar 6, 2024 · 1 comment

Comments

@nikitakovaliov92
Copy link

nikitakovaliov92 commented Mar 6, 2024

The problem

From javadoc in TextCheck#FULL_TEXT

It's a new default behaviour of $.shouldHave(text) since Selenide 6.5.0.

In fact, this property is not default even in 7.2.0 selenide version

P.S. There is a typo in TextCheck#PARTIAL_TEXT javadoc

Left here for compatibility: use it if you have you too many failing tests after upgrading to Selenide 6.5.0.

Second you may be deleted

Environment

  • Selenide Version: 7.2.0
@asolntsev
Copy link
Member

@nikitakovaliov92 That's true, we still haven't made FULL_TEXT the default value.
There is two reasons:

  1. We just forgot it
  2. I am afraid that it would be too big change that would break too many tests. At least when I enabled it in one real project, all tests were broken. :)

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

No branches or pull requests

2 participants