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
Testing against the actual Piazza SaaS is likely more trouble than it's worth; such tests could be set up to tell us when piazza-api breaks against any future changes to the Piazza API, although.
That being said, testing against a static mock API using responses seems like a much better idea for the time being. This won't tell us when Piazza API changes break piazza-api against Piazza, but it will tell us when bad refactoring breaks piazza-api against the mockup.
The text was updated successfully, but these errors were encountered:
An easier solution might be using vcrpy. You can just set up a bunch of test cases using requests as you normally would and the responses from the API will be automatically saved and used when tests are rerun in the future.
Testing against the actual Piazza SaaS is likely more trouble than it's worth; such tests could be set up to tell us when
piazza-api
breaks against any future changes to the Piazza API, although.That being said, testing against a static mock API using responses seems like a much better idea for the time being. This won't tell us when Piazza API changes break
piazza-api
against Piazza, but it will tell us when bad refactoring breakspiazza-api
against the mockup.The text was updated successfully, but these errors were encountered: