How do you prepare bug report in software testing?

A bug report in software testing typically includes the following key elements:

1. Title/ID: A clear, concise title or unique bug ID.
2. Description: A brief explanation of the issue.
3. Steps to Reproduce: A detailed list of actions that lead to the bug.
4. Expected Result: What should happen.
5. Actual Result: What actually happens.
6. Severity/Priority: The impact level of the bug (e.g., critical, minor).
7. Environment: The hardware, software, and versions where the bug occurs.
8. Attachments: Screenshots, logs, or videos (if applicable).
9. Status: Current state of the bug (e.g., Open, In Progress, Resolved).

This structured approach helps developers understand and fix the issue quickly.