“I found a bug and wrote a report, but the developer said, ‘I don’t get it.’” Sound familiar? Here’s a structure that helps you explain an issue clearly on the first try:
📌 Title: What happens, where, and under what conditions?
Bad: “The website doesn’t work.”
Good: “No error message appears on the /login page when a user enters an incorrect password.”
📌 Steps to reproduce
Use a numbered list. Write it as if you're giving instructions to someone who has never seen the app before.
📌 Actual result
Describe what happened.
📌 Expected result
Describe what should have happened.
📌 Attachments
Include a screenshot, video, or log – anything that helps the developer investigate the issue faster.
🤝 Your next step:
Find a bug on any website and write it up using this structure. It’s a skill that will come in handy in an interview.
🧠 Ask AI:
“Here is a bug report I wrote. Rate its clarity and completeness on a scale of 1 to 10, then tell me how I can improve it: [insert your text]”
@andersen_courses ✈