Tests should create their own temporary working directories, rather than relying on _trial_temp
Open
Nobody has claimed this yet.
enhancement
new
priority-normal
trial
- Dominant language
- Python
- Stars
- 6k
- Forks
- 1.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 10
Description
 |
@jml reported |
|---|---|
| Trac ID | trac#2916 |
| Type | enhancement |
| Created | 2007-11-20 19:11:20Z |
Relying on _trial_temp is bad, because tests that inherit from Twisted's TestCase often need to be used in other runners.
Searchable metadata
trac-id__2916 2916
type__enhancement enhancement
reporter__jml jml
priority__normal normal
milestone__
branch__
branch_author__
status__new new
resolution__None None
component__trial trial
keywords__
time__1195585880000000 1195585880000000
changetime__1427887079665027 1427887079665027
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 locating Twisted's TestCase implementation and the tests that reference _trial_temp. Run the affected test suite and inspect how temporary paths are currently provided. Done means tests create their own temporary working directories and remain usable under runners other than trial.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100