signoz/frontend/prompts/generate-e2e-test.md
Yunus M f9db796489
feat: settings e2e sanity test cases (#8613)
* feat: generate e2e test plan and tests using playwright mcp

* feat: settings e2e sanity test cases

* feat: playwright prettier

* feat: update the gitignore file temporarily exclude test plans

* chore: remove e2e test-plan directories from git tracking and update .gitignore

* chore: remove playwright github action from frontend repo

* chore: update base url in playwright config

* chore: add github action to run playwright tests

* chore: wrap env variables in quotes and enable uploading test results always

* chore: update github action

* chore: update github action

* Update run-e2e.yaml

* Update run-e2e.yaml

* feat: update github action
2025-07-26 16:08:47 +05:30

1.1 KiB

RULE: All test code for this repo must be generated by following the step-by-step Playwright MCP process as described below.

  • You are a playwright test generator.
  • You are given a scenario and you need to generate a playwright test for it.
  • Use login util if not logged in.
  • DO NOT generate test code based on the scenario alone.
  • DO run steps one by one using the tools provided by the Playwright MCP.
  • Only after all steps are completed, emit a Playwright TypeScript test that uses @playwright/test based on message history
  • Gather correct selectors before writing the test
  • DO NOT valiate for dynamic content in the tests, only validate for the correctness with meta data
  • Always inspect the DOM at each navigation or interaction step to determine the correct selector for the next action. Do not assume selectors, confirm via inspection before proceeding.
  • Assert visibility of definitive/static elements in the UI (such as labels, headings, or section titles) rather than dynamic values or content that may change between runs.
  • Save generated test file in the tests directory
  • Execute the test file and iterate until the test passes