pytest-dev / pytest-dev/pytest-bdd
generate-missing is not documented
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.5k
- Forks
- 251
- Avg merge
- 43m
- Merged PRs (30d)
- 2
Description
Hi, I finally had a good reason to use pytest-bdd in detail and it's a great experience, so thank you 😊
I saw some comments about generate-missing in the issues and I see something like this in the code, although it doesn't seem to be documented. Is it different to pytest-bdd generate foo.feature? For example does it only do the generate for steps/scenarios that are not yet implemented?? That would be nice :)
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 the generate-missing implementation in the pytest-bdd code and compare its behavior with pytest-bdd generate foo.feature. Document what generate-missing does, including whether it affects only unimplemented steps or scenarios, and explain how it differs from the existing generate command.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, documentation, testing
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100