playfulprogramming / playfulprogramming/hoof
Create an E2E test for a pull request sync
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 9
- Forks
- 7
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 23
Description
Write an E2E test that sends a pull_request webhook to the server with known base/head sha values.
Implement (mock) the github comparison API call for base...head to return a diff with a post, collection, and author.
Then implement the bare minimum details for those post/collection/author sync jobs to pass.
Finally, assert that all three were created and are exposed in the content APIs. (note that these items will be noindex, so by default they won't be returned from the list routes)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the E2E test setup, the server's pull_request webhook handler, and the content APIs. Mock the GitHub comparison API for the known base...head values, then trace the post, collection, and author sync jobs to identify the minimum details they require. Done means the test confirms all three records are created and exposed through the content APIs despite being noindex.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, typescript
- Domain
- api, backend, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100