Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
[ML] API integration tests for UPDATE data frame analytics endpoint #72710
[ML] API integration tests for UPDATE data frame analytics endpoint #72710
Changes from all commits
73e7986
668d3ab
e822d15
defc6bd
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
At first glance it would be hard to know
fetchedJob.description
should equaleditedDescription
based on the variable name, even though I know we already made a request to update the job to that editedDescription earlier. I wonder if it would be clearer toexpect fetchedJob.description to not eql requestBody.description
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.
I think I prefer to have an explicit check for the description so we know it hasn't been changed in any way. A not equal check could potentially miss any undesired changes to the description.
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.
I agree with @alvarezmelissa87 - we should stay with the explicit checks. The only thing that comes to my mind for making it more clear, is to maybe rename
fetchedJob
toupdatedJob
?