PolicyEngine / PolicyEngine/policyengine-api
Expand live simulation integration coverage across US and UK
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 18
- Forks
- 33
- Avg merge
- 23h 40m
- Merged PRs (30d)
- 22
Description
In #2384, we're looking to remove the Oregon rebate tests, which merely run the simulation over a particular policy. These tests are slow and can be clunky, so I think we should proceed with #2384, but they do serve as a basic integration/smoke test that ensures simulations run properly and they did successfully catch issues in #2398.
We should create one or more simulation integration tests. What I'd propose is more than 1, but fewer than 6, targeted at certain very important key policies. The list should include the following policies:
- The US Earned Income Tax Credit and/or Child Tax Credit
- The UK Universal Credit
- A bracketized policy (e.g., income tax)
- A state policy in a state with a high level of overall tax complexity (I'd nominate some program in California)
And should simultaneously deal with the following configurations:
- A standard US run
- A standard UK run
- A US state run
- A UK national run (i.e., England, Wales, Scotland, or Northern Ireland)
I do think we should remove the Oregon tests, but wait to merge #2388 until we can add at least one more relevant integration test.
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
Start by reading #2384, #2388, and #2398, then locate the existing Oregon simulation tests and their integration-test setup. Define one or more tests covering the listed US and UK policies and run configurations, while preserving basic simulation smoke coverage. Done means the new tests pass and provide coverage before the Oregon tests are removed through #2388.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend-api-design, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100