Open
Conversation
…EADME with the setup instructions, installed needed dependencies
…ration.test.js file
TiaMarieG
reviewed
Nov 13, 2025
| test("opens and closes clear drawing dialog", () => { | ||
| render(<PixelForm />); | ||
|
|
||
| // Find the Clear icon and click its parent button |
There was a problem hiding this comment.
Remember to remove comments before pushing code. The it() area should probably describe what these tests do
TiaMarieG
reviewed
Nov 13, 2025
| testEnvironment: "jsdom", | ||
| transform: { | ||
| "^.+\\.[tj]sx?$": ["babel-jest", { configFile: "./babel.config.js" }], | ||
| }, |
There was a problem hiding this comment.
I suggest using Vitest for the front end instead of Jest as Jest is experimental when it comes to ESM/Modules and causes more issues while Vitest is very React friendly
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
4 participants
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.
Diana K. & Laura V.
🧩 Summary
This PR adds unit testing coverage for both the frontend and backend of the project.
Tasks 1 and 2 (Backend Unit Tests and Frontend Unit Tests) have been completed successfully.
However, we encountered some ongoing challenges while working on Task 3 (Integration Tests) and Task 4 (End-to-End Tests).
🧪 Tasks Overview
✅ Task 1: Backend Unit Tests
Implemented unit tests for the Node/Express backend using Jest.
Highlights:
package.json✅ Task 2: Frontend Unit Tests
Implemented tests for React components using Jest and React Testing Library.
Highlights:
We began setting up integration tests to verify backend API endpoints with a test database.
Issues Encountered:
Started setting up Cypress for E2E testing to cover full user flows.
Issues Encountered:
🛠️ Technologies Used
✅ Frontend and backend unit tests run successfully and pass all cases.
❌ Integration and E2E testing require further debugging and setup refinement.