-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Result JSON: SQL without RWI list #9593
Comments
Hey @lenok2018 ! Thanks for raising this feature request -- we've captured this feedback for our internal backlog. I've leave this issue open for the next week if you have any additional context you'd like to provide. 🙇 |
+100500 we need this tooooooooooooooo! |
Please resolve it! |
Please fix it as soon as you can. It causes issues for our team as well (( |
Will be brilliant to have some kind of a toggle for Unexpected list |
Hello team.
Our team faces an unpleasant experience, using "expect_column_values_to_not_be_null" check with Prod data.
Prod DB tables contain a lot of null values now, so running GE test suits we obtain result JSON with thousands RWI in section Result format--> unexpected_list with COMPLETE setting.
We know that its an expected behavior of Complete setting, but this affects out result json significantly.
So, we are asking for new feature to provide the SQL without all this unexpected list rows.
Maybe it could be an additional Keyword argument, which can switch off Unexpected list specification or some other decision.
Please, review the example of our json file - there are more than 40000 RWI in unexpected list:
The text was updated successfully, but these errors were encountered: