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
One of our tests, GoogleBooksApiTest, uses the actual Google API endpoint for testing. Unfortunately, this has been found to change. We need to replicate the responses using our own embedded server and point the GoogleBooksApiTest to our embedded test server.
The text was updated successfully, but these errors were encountered:
Yes and, in fact, this should go along with the embedded test server. I suggested to replicate the Google Books API, because it returns a massive amount of data compared to the Sushi API. There were problems (related to character encoding, for example) when I called the Google Books API. By copying at least one call to our embedded server, we guarantee that the data won't change across different test runs.
One of our tests,
GoogleBooksApiTest
, uses the actual Google API endpoint for testing. Unfortunately, this has been found to change. We need to replicate the responses using our own embedded server and point theGoogleBooksApiTest
to our embedded test server.The text was updated successfully, but these errors were encountered: