Create e2e test for billing
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 88
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Description
**What's the problem? (required)**
When a deployment breaks billing, we don't know it.
**What's the current behavior? (required)**
No alerts when a deploy breaks billing. So we only find out when customers tell us.
Contributor 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.
Research direction
No file, test entry point, or existing billing flow is named in the issue. Start by locating the current end-to-end test setup and billing behavior, then define a deployment-break scenario whose failure is detected by the test; done means the scenario runs reliably and catches the reported regression.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- payments, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100