[FEATURE]: Testing/E2E-Proposal to integrate Cypress.js E2E test suite for critical user flows

Abierto
#183 2 comentarios 0 reacciones 0 asignados Ver en GitHub

@SYED-IRTEZA-HUSSAIN-RIZVI ya está trabajando en esto.

Desde el 13/11/2026.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
30/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
cypress, github-actions, node.js, typescript
Área
ci-cd, testing

Línea de trabajo

Read BestPracticesChecklist.md for the testing requirements this issue cites, then check package.json for existing scripts and the workflow files under .github/workflows to see how CI is wired. The work is to add cypress.config.ts, specs under cypress/e2e/, helper utilities for cy.intercept() mocks of the FastAPI streaming endpoints, the two npm scripts, and a CI job. Done means the suite runs headless in CI against mocked backends and covers routing, form submission, streaming states, responsive viewports and error fallbacks.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

enhancement
Feature and its Use Cases
What is the feature?

Introduce a dedicated Cypress.js-based automated End-to-End (E2E) testing suite for the Perspective frontend application, along with a GitHub Actions CI workflow to automatically execute tests on pull requests and commits targeting main branches.

Why is it needed?

The frontend contains dynamic streaming components, responsive user interface flows, interactive perspective analysis cards, form submissions, and multi-viewport layout handling. Without automated end-to-end testing, UI updates and refactoring can silently introduce user-facing regressions that are difficult to catch through manual verification alone.

The test infrastructure will provide:

  1. Automated E2E regression coverage for critical user journeys
  2. Faster feedback cycles during frontend development and code reviews
  3. Deterministic test execution by mocking network responses (cy.intercept()) for backend FastAPI streaming endpoints
  4. Multi-viewport layout validation across desktop and mobile screen sizes
  5. Continuous execution and assertion through automated GitHub Actions CI workflows
  6. A maintainable foundation for future frontend testing expansion

The initial test suite should cover:

  1. Core page routing and navigation bar interactions
  2. Input form submission and state transition handling
  3. LLM streaming state simulation with intercepted mock API responses
  4. Responsive layout behavior across mobile and desktop viewports
  5. Error handling UI and graceful fallback states for API/network failures
  6. External dependencies and backend API calls (such as FastAPI analysis endpoints) should be intercepted or isolated where appropriate so frontend E2E tests do not depend on live backend uptime, API keys, network latency, or rate limits.

Expected Outcome

  1. Dedicated frontend Cypress.js E2E test suite setup (cypress.config.ts, cypress/e2e/ specs, and helper utilities)
  2. Clean npm scripts added to package.json (npm run test:e2e and npm run test:e2e:open)
  3. Automated frontend test execution integrated into GitHub Actions CI
  4. High-priority user journey coverage isolated from external API dependencies via mocking
  5. A solid testing foundation for progressively expanding E2E coverage as new features are added

Scope: This issue is limited to frontend end-to-end testing infrastructure, Cypress configuration, spec file creation, and CI workflow integration. It does not modify the application's production behavior or introduce new user-facing features.

Additional Context

This feature directly supports the automated testing requirements outlined in BestPracticesChecklist.md: particularly around test invocation, automated CI validation, and end-to-end test coverage.

Additional Context

No response

Code of Conduct
  • I have joined the Discord server and will post updates there
  • I have searched existing issues to avoid duplicates
Lenguaje dominante
TypeScript
Estrellas
58
Forks
90
Merge medio
11 h 51 min
PR fusionados (30 d)
3

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de AOSSIE-Org/Perspective

Todos los issues de AOSSIE-Org/Perspective

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.