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
Please either leave a thumbs up, thumbs down, or any other reaction, or respond with a comment.
For the next phase of Guzzler, I'd really appreciate feedback from anyone interested in the project. For a full description of an upcoming project Road Test, please see the related page on the documentation site; Road Test
This idea is very strongly based on PHPUnit's coverage report. However, instead of keeping track of lines of code executed in a test, it would keep track of endpoints hit and response codes returned from those endpoints. By doing so, a report can be generated afterwards that your code is in fact accounting for each endpoint you intent to, and any error status codes you want to ensure are accounted for. For example, you can verify your code handles responses for 200, 500, and any other status code from the endpoint /example/api/v2/companies/14968.
This project would need to come after Drive is completed enough to handle recording of endpoints and statuses. If Drive can be thought of as a mechanism to do contract testing, then Road Test is the result and proof that all corners are covered that were wanted.
Again, please leave a reaction or any thoughts on this issue. Feedback is helpful.
The text was updated successfully, but these errors were encountered:
I'm closing this issue because it doesn't seem that anyone is interested in voicing an opinion at this time. Guess I'll build something I want and see how the community receives it.
Please either leave a thumbs up, thumbs down, or any other reaction, or respond with a comment.
For the next phase of Guzzler, I'd really appreciate feedback from anyone interested in the project. For a full description of an upcoming project
Road Test
, please see the related page on the documentation site; Road TestThis idea is very strongly based on PHPUnit's coverage report. However, instead of keeping track of lines of code executed in a test, it would keep track of endpoints hit and response codes returned from those endpoints. By doing so, a report can be generated afterwards that your code is in fact accounting for each endpoint you intent to, and any error status codes you want to ensure are accounted for. For example, you can verify your code handles responses for
200
,500
, and any other status code from the endpoint/example/api/v2/companies/14968
.This project would need to come after
Drive
is completed enough to handle recording of endpoints and statuses. IfDrive
can be thought of as a mechanism to do contract testing, thenRoad Test
is the result and proof that all corners are covered that were wanted.Again, please leave a reaction or any thoughts on this issue. Feedback is helpful.
The text was updated successfully, but these errors were encountered: