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 big enhancement to this project, would be to allow to HTTP POST coverage objects to the server by ID. The most common ID I think to use would be a Git commit ID.
So the results could be retrieved via:
GET /coverage/<id>
This would allow developers to have a running server that was solely responsible for displaying test coverage results, and we could see the coverage results for each different commit.
Otherwise..we might have to spin up a new server for each commit, and that's just not very seamless.
AFAICT this would be a huge win for this project.
So when POSTing results, it would be something like:
One big enhancement to this project, would be to allow to HTTP POST coverage objects to the server by ID. The most common ID I think to use would be a Git commit ID.
So the results could be retrieved via:
GET /coverage/<id>
This would allow developers to have a running server that was solely responsible for displaying test coverage results, and we could see the coverage results for each different commit.
Otherwise..we might have to spin up a new server for each commit, and that's just not very seamless.
AFAICT this would be a huge win for this project.
So when POSTing results, it would be something like:
To make minimal changes to code base, we could pass the id as a query string parameter.
The text was updated successfully, but these errors were encountered: