You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With single-method tests, it depends how Test API methods (unrelated to memory) #2 goes. We see in array-api-tests that Hypothesis-powered tests per method end up covering a lot of manual testing anywho, in a much more maintainable/generalised way that also covers test cases we never think of.
A "complete" test per method covers basic interactions, e.g. you don't need to test whether you can get a column name and then access those columns, if you correctly test each step separately.
There are possibly interactions which aren't like that... a TODO is to identify what they are.
So a TODO for me is to properly review each of the listed test suites to see where inspiration can be taken from. Probably if #1 and/or #2 doesn't end up being that worth, just copying tests to have the coverage is nice, even if the test cases in dataframe-interchange-tests don't have clearly distinct test cases like I think array-api-tests does.
The text was updated successfully, but these errors were encountered:
Efforts have already been made to test the df interchange protocol
Do we fold them in to this test suite?
array-api-tests
that Hypothesis-powered tests per method end up covering a lot of manual testing anywho, in a much more maintainable/generalised way that also covers test cases we never think of.So a TODO for me is to properly review each of the listed test suites to see where inspiration can be taken from. Probably if #1 and/or #2 doesn't end up being that worth, just copying tests to have the coverage is nice, even if the test cases in
dataframe-interchange-tests
don't have clearly distinct test cases like I thinkarray-api-tests
does.The text was updated successfully, but these errors were encountered: