Testing/ticket 86e13hweg create cypress tests#68
Open
jj-javascript wants to merge 3 commits into
Open
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Feature Summary
Summary:
3107a80→4aa70c9Range note:
git log 3107a80..4aa70c9shows 2 commits (cadaca5,4aa70c9). The narrative below covers three commits on that line:3107a80(start),cadaca5, and4aa70c9(end).1.
3107a80— Cypress Tests for landing page created and working(Wed Apr 29, 2026)
cypress.config.ts(component config, webpack/Next wiring).cypress/component/LandingPage.cy.tsx(landing / upload-related UI checks).cypress/support/component.ts,component-index.html,commands.ts,cypress/mocks/next-navigation.ts, logging mock, example fixture.next.config.jsfor Cypress/Next compatibility.cypress/screenshots/...that had been committed from earlier runs.2.
cadaca5— Upload feature spec test(Wed Apr 29, 2026)
cypress/component/UploadForm.cy.tsx(~227 lines) covering file upload, mobile layout, language swap, submit state, etc.cypress.config.ts(~50 lines removed) — config simplified relative to the prior commit.cypress/mocks/next-navigation.ts(mock router aligned with new tests).cypress/support/logging-stub.tsand the remaining failed screenshots from the repo.3.
4aa70c9— cypress e2e tests for document translation check and text-to-speech feature check(Thu Apr 30, 2026)
cypress/e2e/translate.cy.ts— translate page session handling, API error paths, loading, success.cypress/e2e/translation-tts.cy.ts— multilingual pairs, Read Aloud / TTS (mocked APIs), workflow tests; helpers for unique doc IDs, summarize stub, WAV mock, etc.cypress/support/e2e.ts, andcypress.config.tsupdates fore2e(baseUrl, spec pattern, support file).package.json/ lockfile — addedcypress,start-server-and-test, and npm scripts for running Cypress (including translation-tts + dev server on port 3055).components/features/tts/ReadAloudPanel.tsx— split autoplay-blocked UX (“Ready to play”) from real TTS failures (“Read Aloud failed”) so tests and users aren’t misled by browser autoplay policy.logs/logs.jsonupdated (runtime/API log noise from local runs).Overall arc
3107a80cadaca54aa70c9What does this PR change?
This PR creates consistent Cypress tests for the main components of the application.
Why was this change made?
This change makes debugging easier in the future.
What is the code meant to do?
To have self-administering tests that catch any issues that happen as the app runs or the architecture is expanded in the future.
Feature Team / Lane
Team #: (1–5)
DevOps Lane: (if applicable)
Type of Change
Testing
How was this tested?
Automated Testing
Manual Testing
Screenshots (if UI changes)
Attach screenshots or screen recordings here if the PR includes UI changes.
Risks / Edge Cases
Risks would be if any integral parts of the UI/UX changes or if other languages are added tests would have to be refactored.
Environment Variables Added or Changed
List variable names only. Do not include secrets.
Checklist