RFC: Postgres-backed integration tests in CI
Maintainers usually reply within 1 day
A pull request for this has already been merged.
- #187 by @natos — merged
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- github-actions, next.js, postgresql, typescript
Research direction
Start by reading ADR-0011, ADR-0016, and ADR-0017, then inspect the existing CI workflow and database test setup. The RFC proposes a Postgres service container and integration coverage for account deletion, repeat and concurrent feedback prompt issuing, email failures with a fake provider, and cron authentication. Done means those scenarios run in CI and cover the database and platform failures described.
Written by the indexing model from the issue text.
Description
The coverage gate (ADR-0011) guards pure logic in src/lib, but the recent incidents happened where code meets the database and the platform: crons returning 405 (#138), duplicate emails (#154), a foreign-key failure on account deletion (#149). Today's fixes (ADR-0016, ADR-0017) were verified by recorded manual runs against a throwaway Postgres — locks, transactions, rollback, concurrency.
Proposal (RFC): a CI job with a Postgres service container running a small integration suite: account deletion, feedback prompt issuing (repeat + concurrent runs, email failures via a fake provider), cron auth. Moderate cost; closes the gap the coverage gate can't see.
- Dominant language
- TypeScript
- Stars
- 3
- Forks
- 6
- Avg merge
- 13h 29m
- Merged PRs (30d)
- 56
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
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.
More from grasshopper-protocol/grsshppr
-
bug UX
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
grasshopper-protocol/grsshppr#209 ·
Maintainers usually reply within 1 day
-
Add tests for utils.ts cn() functionPossibly taken @yogesh201sits claimed this 7 days ago. Opengood first issue testing
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
grasshopper-protocol/grsshppr#81 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
-
code quality documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
grasshopper-protocol/grsshppr#78 ·
Maintainers usually reply within 1 day
-
a11y documentation good first issue UI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
grasshopper-protocol/grsshppr#77 ·
Maintainers usually reply within 1 day
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
grasshopper-protocol/grsshppr#46 ·
Maintainers usually reply within 1 day
All issues in grasshopper-protocol/grsshppr
Similar issues
-
Plugin: sheet music can't be scrolled by hand before playbackPossibly taken @snakajima claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
receptron/jinglescript#51 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 9 days
-
clawsweeper:needs-maintainer-review clawsweeper:needs-product-decision clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
openclaw/openclaw#186424 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
chore(worker): five module header comments describe the code from before later issues changed itOpenarea:dev U2-later
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
bentleypark/aiwatch#1824 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Pal-AI-Lab/Coopanion#469 ·
Maintainers usually reply within 1 day