Bughound

Background

This was a semester project for my software testing course (CECS 544). We needed a bug tracker that didn't drown you in features: report a defect, assign it, attach evidence, track it to resolution. I owned both the interface and the server logic.

Solution

React frontend talking to a backend running on Bun. Editable tables for managing programs and employees, login, and file attachments on bug reports so fix context lives in one place. Every report moves through a defined status flow from submission to resolution.

Process

I designed the relational schema first: employees, programs, functional areas, and how they map onto reports. Frontend and backend stayed separate, with migrations keeping the schema stable as features landed. A lot of time went into form ergonomics and making uploads actually work end-to-end.

Final Product

Reflection

This was my first serious time with Bun as a runtime, and it sold me on fast tooling. The lesson that stuck: get your data types consistent early or you'll pay for it later. With more time I'd add notifications and better filtering.