Check for functionality, bugs, and alignment with the assigned task.

Step 1 – Understand the Task Before Testing

Before testing, make sure you fully understand what you’re reviewing:

1. Check the assigned task in the tracker (Jira, Google Sheet, etc.).
2. Read the task details – What was the issue raised for this task?
3. Clarify the goal – What do we want to be able to do on this page after this task is done?
4. If you don’t understand the task, ask your product manager before testing.

Step 2 – Test for Functionality

This is simply asking: Does it work the way we expected?

How to do it:

1. Open the page or feature where the task was implemented.
2. Follow the normal steps a user would take.
3. Example steps to take (process flow):
   1. Click the login button.
   2. Enter your email and password.
   3. Press submit.
   4. See if it takes you to the dashboard.
4. If something doesn’t work or feels wrong, note it immediately.

Step 3 – Check for Bugs & Alignment With the Task

While testing, also check if everything matches what was assigned:

1. Is the page or feature working as described in the tracker?
2. Is the design/layout correct?
3. Does it work on both desktop and mobile?
4. Are there any broken elements, missing text, or unexpected errors?

Step 4 – Recording Issues in the Issue Log

The Issue Log is where we record all issues – not just from current sprint testing. It should include:

1. Bugs found during task testing.
2. Random bugs found outside sprint work.
3. Customer feedback that reports an issue.

For each issue, log:

1. Title (short description)
2. Steps to Reproduce (how you got the issue)
3. Expected Result (what should have happened)
4. Actual Result (what happened instead)
5. Evidence (screenshot or short video)

Step 5 – If the Issue is from the Current Sprint

When testing a sprint task, if you find an issue:

1. Kickback the task – change its status to “Kickback” in the tracker.
2. Add a comment directly to the ticket/tracker
   1. describing the issue,
   2. steps to recreate the issue,
   3. expected result and
   4. actual result.

If the task passes your testing but needs PM review:

1. Change status to “Final Review”.

Step 6 – Reporting Priority Issues

1. Use the Issue Log for all regular issue tracking.
2. Only flag priority issues directly to the PM or developer immediately.
3. Demo priority issues if needed so there’s no confusion.

✅ Key Rule:
If it’s not matching the assigned task or working as expected, it’s not done – no matter how small the issue looks.