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
I would like to discuss an easier way to test github apps. I can see other github bots trying to do the same and test their applications with slightly different approaches. It would be best to unify this process.
There could be 2 main areas to improve on this.
Create JSON processors for most common events such as Pull Request. It will make tests more readable and configurable without the need of having many slightly different *.json payloads with Pull Requests.
Create easier mocking for most common cases and events (similarly to first point)
Example of mocking builder (In case the PR was updated please use this link and find file MockedGHPullRequestProcessor). Builder and usage
We would need to find a trade-off between mocking too much and covering just the basics. Also we could provide mocking for classes not extending GHObject as they are not able to use GitHubMockContext#ghObject mocking method such as GHPullRequestCommitDetail.
I would like to discuss an easier way to test github apps. I can see other github bots trying to do the same and test their applications with slightly different approaches. It would be best to unify this process.
There could be 2 main areas to improve on this.
*.json
payloads with Pull Requests.Example of JSON processor in our repo
Example of mocking builder (In case the PR was updated please use this link and find file MockedGHPullRequestProcessor). Builder and usage
We would need to find a trade-off between mocking too much and covering just the basics. Also we could provide mocking for classes not extending
GHObject
as they are not able to useGitHubMockContext#ghObject
mocking method such asGHPullRequestCommitDetail
.Quick links to quarkus and hibernate bots
The text was updated successfully, but these errors were encountered: