SpecFlowOSS
Improve Driver Pattern Documentation
As I was reading through the Driver Pattern documentation, I realized that it could be improved to drive home the potential benefits of using the approach.
Types of changes
I've rejigged the introduction to the article.
- [ ] Bug fix (non-breaking change which fixes an issue).
- [ ] New feature (non-breaking change which adds functionality).
- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected).
- [ ] Performance improvement
- [ ] Refactoring (so no functional change)
- [x] Other (docs, build config, etc)
Checklist:
- [ ] I've added tests for my code. (most of the time mandatory)
- [ ] I have added an entry to the changelog. (mandatory)
- [ ] My change requires a change to the documentation.
- [ ] I have updated the documentation accordingly.
not entirely sure why the one check wasn't successful - if anyone know where to check logs that would be appreciated!
@SabotageAndi any chance you might know who is best to get this reviewed?
Also noticing other PRs with the same issue as what I've mentioned above
@thatstatsguy Sadly I can't help you. I don't know anybody at Tricentis that is working on SpecFlow anymore.
You have probably more luck in switching to Reqnroll (https://github.com/reqnroll/Reqnroll/) and send the PR there.
appreciate the response @SabotageAndi ! pity that the repo isn't getting much attention
