Reorganise Trial tests
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6k
- Forks
- 1.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 10
Description
 |
@jml reported |
|---|---|
| Trac ID | trac#2237 |
| Type | task |
| Created | 2006-11-18 23:34:36Z |
The problem is that I have no clue where to find the test for a given piece of code. Also, I suspect Trial is overtested in areas (where 'overtested' means a single behaviour is directly tested in many places).
Trial's tests should be organised so that tests for things in runner.py should be in test_runner.py and so forth.
Of course, that would leave us with only five test modules. So perhaps there is a more logical breakdown.
Searchable metadata
trac-id__2237 2237
type__task task
reporter__jml jml
priority__normal normal
milestone__
branch__
branch_author__
status__new new
resolution__None None
component__trial trial
keywords__
time__1163892876000000 1163892876000000
changetime__1163892876000000 1163892876000000
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 inventorying Trial's test modules and comparing them with the implementation files, especially runner.py and the proposed test_runner.py. Identify duplicated behavior coverage and propose a logical grouping beyond the five-module split mentioned in the issue. Done means the Trial tests have a clear mapping to the code they cover without redundant direct tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100