Before Creating an Issue:
- Make sure you're using the most up-to-date version of the
webdriver_test_toolspackage (e.g. runpip install --upgrade webdriver_test_tools)- Check the open GitHub Issues to see if the issue has already been reported
- If the issue hasn't been reported yet but appears to be related to Selenium, check Selenium's GitHub Issues to see if the issue has already been reported
If the issue isn't reported there and appears to be specific to WebDriver Test Tools, open a new issue and fill out the required details, being as specific as possible.
Before Creating a Feature Request:
- Check the open feature requests to see if the feature has already been requested
- If the feature hasn't already been requested, open a new feature request
Note:
The project is currently the in early stages of development, and as such the workflow for pull requests hasn't been formalized. These guidelines are a work in progress and will be expanded upon as the project develops.
- Formalize feature branch workflow
There are 2 main branches for this project:
- master: The main branch where source code is ready for production
- develop: The working branch for the next release
New features for upcoming releasese should have their own feature branch. When development on the feature is finished, a pull request should be submitted to merge into the develop branch.
Once the develop branch is at a stable point and is ready for release, it will be merged into master and tagged with a release number.