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

Assertions that use the LogicalNot constraint (assertNotEquals(), assertStringNotContainsString(), ...) can generate confusing failure messages #5516

Closed
sebastianbergmann opened this issue Sep 17, 2023 · 0 comments
Labels
feature/assertion Issues related to assertions and expectations type/bug Something is broken

Comments

@sebastianbergmann
Copy link
Owner

Assertions such as assertNotEquals(), for example, use LogicalNot::negate() to generate failure messages.

When the string that is to be transformed contains words such as contains or exists then the transformation generates confusing failure messages.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature/assertion Issues related to assertions and expectations type/bug Something is broken
Projects
None yet
Development

No branches or pull requests

1 participant