-
Notifications
You must be signed in to change notification settings - Fork 152
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
Then its key condition be value doesn't work correctly #225
Comments
Thanks for the issue @melcloud 🎉 I thought, I fixed this issue yesterday with 1.1.10! Having a look quickly. |
Fixed the problem, waiting for all functional tests to pass, then will release it asap. |
Just released 1.1.11. Could you please have a try and let me know ? Thanks! |
I can confirm this had been fixed. Thanks for the quick response! |
This issue's conversation is now locked. If you want to continue this discussion please open a new issue. |
Description :
When using "Then its key condition be value", it doesn't perform exact match
To Reproduce
Expected behavior :
Expect the above scenario to fail as mesh_name should be demo2
Tested versions :
Additional context
Looks like the "Then its key condition be value" is partial match on value (like starts with). Because if I change the above to "Then its mesh_name must be demofoo", it fails as expected.
The old filter syntax works as expected. Following scenario failed as expected when using filter:
The text was updated successfully, but these errors were encountered: