Gather Twisted testing patterns into a common module
Open
Nobody has claimed this yet.
bug
core
new
priority-high
- Dominant language
- Python
- Stars
- 6k
- Forks
- 1.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 10
Description
 |
@jml reported |
|---|---|
| Trac ID | trac#1945 |
| Type | defect |
| Created | 2006-07-21 03:58:05Z |
It seems that a lot of tests do a lot of things the same, and should represent this by using the same code.
Maybe people who write code that uses Twisted will also want to use this code.
This comment deliberately left vague.
Searchable metadata
trac-id__1945 1945
type__defect defect
reporter__jml jml
priority__high high
milestone__
branch__
branch_author__
status__new new
resolution__None None
component__core core
keywords__
time__1153454285000000 1153454285000000
changetime__1366631249000000 1366631249000000
version__None None
owner__
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 surveying Twisted's test suite for repeated testing patterns and documenting which cases are genuinely shared. Define the scope of a common module before changing callers; done means the selected patterns are consolidated without losing existing test coverage, and the module is usable by code that depends on Twisted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100