I actually never do QA report for a company or an event before, but i did do one for my university project where we have to make one as a mock example on what will we do if there's an error in the website that we make:

QA Bug Report Example

Project: Cybersecurity Educational App Report

Date: December 16, 2024

Tested By: Erwin Okto Wu

Environment:

Device: Lenovo IdeaPad Flex 5i OS: Windows 11 (22H2)

Browser: Google Chrome (Version 122.0.6261.94)

App Version: v1.2.3 (Beta) Network: 100 Mbps Wi-Fi

Bug Summary: [Critical] Login Button Unresponsive on Mobile Version

Bug Description: When a user tries to log in using the mobile version of the web app, tapping the "Login" button does not trigger any action. This prevents users from accessing their accounts.

Steps to Reproduce: Open the web app on a mobile browser (Chrome, Safari).

Enter valid credentials (email and password). Tap the "Login" button. Observe that nothing happens—no response, loading indicator, or error message.

Expected Result: The app should authenticate the user and redirect them to the dashboard upon tapping "Login."

Actual Result: The button does not respond, and the user remains on the login screen.

No error message is displayed.

Attachments: screenshot and recordings

Severity: Critical (Users cannot log in)

Priority: High (Blocking feature) Additional Notes: Issue occurs on both Chrome and Safari mobile versions. Works fine on desktop. No network request is sent when clicking the button (checked via DevTools). Assigned To: Erwin Okto Wu

Status: Open

I would use exploratory testing and functional testing to find the bugs and document each steps to outline how the bugs occur in the first place while still checking different environments such as different browsers, etc.