This is a simple project utilising 2 UI test automation tools - Playwright and Selenium 4.
The purpose of the project is to compare both tools in implementation and execution of exactly the same tests. Tests are using BE response mocking mechanism.
As SUT, project utilises my Angular UI application called Spec Lead Notes UI deployed on Firebase which uses Spec Lead Notes BE deployed on Render.
The project is organized into following packages:
- common: Common utility files.
- mocks: Objects used in mocking the responses in teh tests.
- model: Model classes.
- playwright: Page components, BE response mocking mechanism Page Objects and test fixture implemented using Playwright.
- selenium: Page components, BE response mocking mechanism and Page Objects implemented using Selenium 4.
- tests: Automation tests implemented using Playwright and Selenium. For both tools, tests logic is exactly the same.
- Jenkinsfile: Jenkins configuration used when tests were run on local instance of Jenkins.
- Run
npm installto install the dependencies. - Run
npm run pw:installto install Playwright browser executables.
Important note - Backend of SUT is hosted on Render. Hosting is free and is has the disadvantage that when deployed service is not used for a specified amount of time, it is turned off and turned on only when pinged again. For below test execution, it means that first test runs will fail but they will trigger BE service to come up. Subsequent test runs should be successful.
- Run
npm run test:seleniumto execute Selenium tests. - Open Selenium test execution report - report.html.
- Run
npm run test:pw:headedto execute Playwright tests in headed mode. - Run
npm run pw:reportto see test execution report generated for Playwright tests.
pw:install: Install Playwright browser executable. Might be needed after Playwright version update.compile:watch: runs Typescript compiler in watch mode meaning you don't have to manually runtsceverytime you change a file.test:pw:ui: Run Playwright in UI mode.