[FEATURE]: Testing/E2E-Proposal to integrate Cypress.js E2E test suite for critical user flows
@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
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
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:
- Automated E2E regression coverage for critical user journeys
- Faster feedback cycles during frontend development and code reviews
- Deterministic test execution by mocking network responses (cy.intercept()) for backend FastAPI streaming endpoints
- Multi-viewport layout validation across desktop and mobile screen sizes
- Continuous execution and assertion through automated GitHub Actions CI workflows
- A maintainable foundation for future frontend testing expansion
The initial test suite should cover:
- Core page routing and navigation bar interactions
- Input form submission and state transition handling
- LLM streaming state simulation with intercepted mock API responses
- Responsive layout behavior across mobile and desktop viewports
- Error handling UI and graceful fallback states for API/network failures
- 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
- Dedicated frontend Cypress.js E2E test suite setup (cypress.config.ts, cypress/e2e/ specs, and helper utilities)
- Clean npm scripts added to package.json (
npm run test:e2eandnpm run test:e2e:open) - Automated frontend test execution integrated into GitHub Actions CI
- High-priority user journey coverage isolated from external API dependencies via mocking
- 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
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de AOSSIE-Org/Perspective
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 83/100
AOSSIE-Org/Perspective#191 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
AOSSIE-Org/Perspective#190 ·
-
[BUG]: Missing input validation in URlRequest and ChatQuery causes 500 crashes and wasteful scraper executionPosiblemente ocupada @agarwalpranav0711 la tomó hace 25 días. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
AOSSIE-Org/Perspective#178 ·
-
[BUG]: chunk_rag_data crashes with ValueError when perspective is a dict, silently dropping RAG vector storagePosiblemente ocupada @agarwalpranav0711 la tomó hace 36 días. Abiertobug
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
AOSSIE-Org/Perspective#175 ·
-
[BUG]: Scraper passes headers as query params in requests.get (User-Agent never sent)Posiblemente ocupada @Th-Shivam la tomó hace 50 días. Abiertobug
Dificultad 1/5 Menos de una hora Aptitud para principiantes 92/100
AOSSIE-Org/Perspective#161 · 1 comentario ·
Todos los issues de AOSSIE-Org/Perspective
Issues similares
-
documentation lens:human needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 73/100
thebristolsound/birdbrain#2246 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
A voting window past about 69.9 million hours stores a deadline that reads back as no deadlineAbiertobug ready-for-human
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
BoardGamesEmpire/board-games-empire-backend#1452 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
good first issue stretch
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
Los mantenedores suelen responder en 1 día