IMGIITRoorkee / IMGIITRoorkee/Ticketify
Implement Jest Tests for Core Functionality
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
### **Description**
Currently, the project lacks **unit tests** and **integration tests** for core functionality such as utility functions, components, and API data handling. Implementing tests using **Jest** will ensure the project's stability and make future feature development safer.
---
### **Tasks**
- Set up any robust testing framework (not confined to **jest**).
- Write Unit Tests for utility functions to confirm that components like `TicketCard` render the right data under different conditions
- Make sure to that utility functions like `getTickets` handle failure scenarios gracefully.
- Document the testing setup
---
### **Acceptance Criteria**
- [ ] A testing setup exists and tests can be executed locally.
- [ ] Critical functions and components are verified under both success and failure cases.
- [ ] Documentation is updated so others can run or write their own tests.
Meanwhile, while writting tests if you figure out any bug or breakage somewhere, feel free to create an issue.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the TicketCard component and the getTickets utility, then inspect how the Next.js app currently handles API data. Establish a test setup that runs locally, cover success and failure cases for the named functionality, and update the project documentation with commands for running and adding tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, next.js
- Domain
- api, frontend, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100