-
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
'_AsyncQuery.cancel' fails to update from returned resource #2377
Comments
@tseaver Germane to this change, I've run the following before to get a sense of our actual usage of
Could be worthwhile to do it and see what code paths we aren't testing against the backend? (NOTE: I'm aware this is using the old |
No I just meant that if you got a sense for lines uncovered during system tests then an error like this would be detectable. The streaming bit was just an example so you could do the same locally. Essentially this error is due to the fact that our code and unit tests make a bad assumption about the payload. |
OK. We don't have any system test which exercises I'm not convinced that we need to get to 100% coverage for system tests, but we should at least have "garden path" coverage for all the API requests. |
Ha. Never heard "garden path" before! I agree having full coverage in system tests isn't necessary (or possible, since error cases may never occur), just wanted to share a script I had used before |
E.g.:
The docs for
job.cancel
show that the job resource is in ajob
subkey of the response.The text was updated successfully, but these errors were encountered: