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
Add the test for TakeDatasetOp #26632
Add the test for TakeDatasetOp #26632
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A couple of minor comments, but overall this looks good to me.
/*breakpoints*/ {0, 2, 5, 11}}; | ||
} | ||
|
||
class ParameterizedDatasetTest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ParametrizedTakeDatasetOpTest
}; | ||
|
||
// Test case 1: take fewer than input size | ||
TestCase TakeFewerTestCase() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TakeLessTestCase
@feihugis Thank you for another unit test! I like that unit test style that we have converged on (defining test cases through functions that return a TestCase). When you get a chance, could you please apply it consistently across the existing unit tests? For instance, I recently made changes to tensor_slice_dataset_op_test.cc and sparse_tensor_slice_dataset_op_test.cc to fix an internal test failure and it would be great if you could apply your test style to those for consistency. Thanks again for the contributions! |
@jsimsa Thanks for your quick review! The class and function names have been updated in this commit. Sure, I will update the existing unit tests this week and keep the test style on the future PRs. |
PiperOrigin-RevId: 238291593
This PR adds the test for
TakeDatasetOp
.cc: @jsimsa @rachellim