Document best practices for integration/functional tests
Open
Nobody has claimed this yet.
documentation
- Dominant language
- Python
- Stars
- 838
- Forks
- 123
- Avg merge
- 7h 58m
- Merged PRs (30d)
- 12
Description
How do I test my klein apps, without using urllib or similar?
Currently I'm considering adapting these Twisted web tests or these ones.
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 reviewing the two linked Twisted web test examples and determine how their approach applies to Klein applications without urllib. The issue names no repository files or existing tests, so first locate the project’s testing documentation and examples. Done means documenting a clear, supported best practice for integration or functional testing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation, testing-qa
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100