Thank you for considering contributing to Playwright-BDD! 🎉
This guide will help you get started with contributing.
There are different ways to contribute.
We encourage you to share your experiences and insights about using Playwright-BDD! BDD workflows can vary widely, and your unique approach could inspire others in the community.
Here are some ways to share your knowledge:
- Write articles on platforms like Dev.to, Medium, or LinkedIn.
- Share interesting findings, tips, and best practices related to Playwright-BDD or end-to-end testing in general.
- Promote your content on the Playwright Discord articles and your social networks to reach a broader audience.
By contributing to the conversation, you'll help grow the Playwright-BDD community and improve testing workflows for everyone!
If you find a bug or have an idea for a feature:
- Check if the issue already exists in the Issues.
- If not, create a new issue!
To contribute code:
- Fork the playwright-bdd repository.
- Clone your fork to your local machine:
git clone https://github.com/<YOUR_USERNAME>/playwright-bdd.git
- Create a new branch for your feature or bug fix:
git checkout -b my-feature
- Perform the development setup
- Make and commit your changes.
- Push the changes to your fork:
git push origin my-feature
- Open a pull request to the
main
branch.
- Install dependencies:
cd playwright-bdd npm install
- Install Playwright browsers:
npx playwright install chromium
- Run tests:
npm t
Use the command below (use TAB after typing test/
to autocomplete the test path):
npm run only test/<%test-dir%>
Example:
npm run only test/special-tags
This command will install the provided Playwright version without saving it to package.json
:
npx cross-env PW=1.45 npm run pw
This command will install chromium
for the current Playwright version, without clearing previous browsers:
npm run pw:browsers
npm show @playwright/test@1 deprecated
npx playwright clear-cache