mozilla-services / mozilla-services/markus
add tests for backends
Open
Nobody has claimed this yet.
help wanted
- Dominant language
- Python
- Stars
- 70
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
We currently have no tests for markus.configure or the backends. We should probably add at least some basic ones.
- test
markus.configurewith zero, one, and multiple backends does the right thing - test
markus.configurewith backend options passes the options in - test
markus.configurewith backend filters passes the filters in - test that filters work on the backends
Probably some other things, too.
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 locating markus.configure, the backend implementations, and the existing test layout. Add focused tests for zero, one, and multiple backends, backend options, backend filters, and filtering behavior; done means these cases pass and any additional required coverage is identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100