External/signoz
1
0
Fork 0
mirror of https://github.com/SigNoz/signoz.git synced 2025-12-17 15:36:48 +00:00
Code Issues Packages Projects Releases Wiki Activity
signoz/frontend/e2e/test-plan
History
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
..
settings
feat: settings e2e sanity test cases (#8613)
2025-07-26 16:08:47 +05:30
README.md
feat: settings e2e sanity test cases (#8613)
2025-07-26 16:08:47 +05:30
validation-report.md
feat: settings e2e sanity test cases (#8613)
2025-07-26 16:08:47 +05:30

README.md

SigNoz E2E Test Plan

This directory contains the structured test plan for the SigNoz application. Each subfolder corresponds to a main module or feature area, and contains scenario files for all user journeys, edge cases, and cross-module flows. These documents serve as the basis for generating Playwright MCP-driven E2E tests.

Structure

  • Each main module (e.g., logs, traces, dashboards, alerts, settings, etc.) has its own folder or markdown file.
  • Each file contains detailed scenario templates, including preconditions, step-by-step actions, and expected outcomes.
  • Use these documents to write, review, and update test cases as the application evolves.

Folders & Files

  • logs/ — Logs module scenarios
  • traces/ — Traces module scenarios
  • metrics/ — Metrics module scenarios
  • dashboards/ — Dashboards module scenarios
  • alerts/ — Alerts module scenarios
  • services/ — Services module scenarios
  • settings/ — Settings and all sub-settings scenarios
  • onboarding/ — Onboarding and signup flows
  • navigation/ — Navigation, sidebar, and cross-module flows
  • exceptions/ — Exception and error handling scenarios
  • external-apis/ — External API monitoring scenarios
  • messaging-queues/ — Messaging queue scenarios
  • infrastructure/ — Infrastructure monitoring scenarios
  • help-support/ — Help & support scenarios
  • user-preferences/ — User preferences and personalization scenarios
  • service-map/ — Service map scenarios
  • saved-views/ — Saved views scenarios