In a course project using a web-based data collection tool, I identified a bug where participant responses failed to save under specific conditions. I documented the issue with clear reproduction steps, expected versus actual behavior, environment details, and screenshots of the error. I also noted the frequency of the bug and its impact on data quality, which helped the team quickly reproduce and fix the issue before additional data were collected.

I approach identifying and documenting bugs by first understanding the intended functionality and confirming that the issue is reproducible. I focus on isolating the problem by testing different conditions and narrowing it down to the smallest set of steps that consistently trigger the bug. When documenting issues, I prioritize clarity and usefulness by clearly outlining reproduction steps, expected versus actual behavior, and relevant context such as environment or user state. My goal is to communicate problems in a way that makes them easy to understand, fix, and prevent, while keeping the user experience at the center of the process.