Add initial Playwright automation#473
Add initial Playwright automation#473tanmay-srivastav4 wants to merge 5 commits intopointblank-club:stagingfrom
Conversation
|
Resolve the merge conflicts |
|
resolved conflicts. please merge it bhaiya. |
|
@tanmay-srivastav4 LGTM from my side can you just run Build and Lint tests and show me the results real quick? |
|
Wait a minute...where did you do tooling of this mcp server? |
this was just a playwright tests orchestration. Building e2e mcp server for it could be done in future |
|
Acha acha...show me the build and lint tests |
a54c649 to
b2c5c0c
Compare
| "strict": true, | ||
| "esModuleInterop": true | ||
| }, | ||
| "include": ["mcp/**/*.ts"] |
There was a problem hiding this comment.
I dont think this is necessary
There was a problem hiding this comment.
yes looked into it again. it isn't required
| { | ||
| "name": "Navbar links are visible", | ||
| "steps": [ | ||
| { "action": "goto", "value": "/" }, | ||
| { "action": "assertVisible", "value": "nav" }, | ||
| { | ||
| "action": "assertVisible", | ||
| "value": "nav >> role=link[name=\"Achievements\"]" | ||
| } | ||
| ] | ||
| } |
There was a problem hiding this comment.
Ummm...I am not sure if this is how it is done
There was a problem hiding this comment.
as far my knowledge, the .json file is used as input for test generation. also we can add more external test if required. when we run, it is converted into a Playwright .spec.ts test and then executed by Playwright like any other test.
|
I have added comments plz fix this |
|
Ggs lgtm...let's hope it doesn't break prod |
|
@slashexx merge this plz |
|
Wait hold |
|
Now this looks clean |
|
@slashexx merge plz |
e413e31 to
7d8e66c
Compare
Summary: What does this PR do?
<!
This PR introduces an initial Playwright-based end-to-end (E2E) testing setup for the website.
It adds route-level browser tests that verify pages are reachable and render correctly in a real browser. The setup is designed to be extensible and supports future automation and test generation workflows without impacting existing development or CI behavior.
-->
Changes Made
Describe the changes you've made in this PR:
Type of Change
How Has This Been Tested?
Describe the tests you ran:
Please describe the test cases and expected behavior:
1.Page load tests – Routes load correctly and render without errors
2. Failure handling – Screenshots, videos, and traces are generated on failure
Screenshots
<!

-->
Dependencies
<!
Added Playwright as a dev dependency
-->