pytest-dev / pytest-dev/unittest2pytest
Output bug reporting howto if result contains syntax-errors
Open
Nobody has claimed this yet.
enhancement
help wanted
- Dominant language
- Python
- Stars
- 141
- Forks
- 28
- PR merge metrics
- No merged PRs in 30d
Description
To allow the tool to be used even with problems like https://github.com/pytest-dev/unittest2pytest/issues/17 and https://github.com/pytest-dev/unittest2pytest/issues/18 , I think it would be helpful to do a syntax parse on the generated file before writing it, so files which will be broken can be skipped.
Contributor guide
No contributing guide indexed for this repository
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
Read the generated-file writing path and the behavior described in issues 17 and 18. Determine where syntax parsing could happen before output is written; done means broken generated files are skipped and a how-to report is emitted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100