ci/cd integration - best practices
Hello guys, now i have some tests running and stable, i would like to add a new optionnal job for the moment in our applicative cd pipeline to trigger plawyright test. I dont find any doc for beginers. I my mind, i have to : -push my test in a specific github repo -From the applicative repo, add a new job to tun the test stored in the other repo.
Am i right ? Thanks a lot
This thread is trying to answer question "How to integrate Playwright tests into a CI/CD pipeline and where to store the tests?"
The official docs are potentially useful here https://playwright.dev/docs/ci
My advice, don't make e2e tests optional, they should be written so that they can be run every time in your pipelines (wherever your strategy dictates they should be run)
Related Discord Threads
- Playwright storageState with github actions and stripemohamad_97530 asked on · 2 messages · unresolved
- How do I run Playwright tests in Github Actions with a database on Docker ?tibo1002 asked on · 2 messages · unresolved
- auth.setup.ts not running (following documentation)augustinsorel asked on · 3 messages · resolved
Rayrun is a community for QA engineers. I am constantly looking for new ways to add value to people learning Playwright and other browser automation frameworks. If you have feedback, email [email protected].