QA Checklist for Testing New Features

My QA Checklist for Testing a New Feature

1. Understand the Requirement

Before testing, I make sure I understand:

• What is the feature supposed to do?
• Who is using it?
• What are the expected results?
• Are there acceptance criteria?
• Are there any known limitations?

2. Test the Happy Path

Start with the normal, expected behavior.

For example, if testing a login feature:

• Enter a valid
• Enter a valid password
• Click Log In
• Confirm the user reaches the correct page
• Confirm the user's information loads correctly

3. Test Invalid Inputs

Then I try to break it.

Examples:

• Incorrect password
• Invalid email format
• Empty fields
• Extremely long input
• Special characters
• Spaces before/after input
• Unexpected characters

4. Test Edge Cases

I ask: "What happens if the user does something unexpected?"

Examples:

• Double-clicking a button
• Refreshing during an operation
• Losing internet connection
• Using the feature on a very small screen
• Entering the maximum/minimum allowed value
• Leaving the page and coming back

5. Check UI & UX

I verify that the feature:

• Looks correct
• Is responsive
• Has readable text
• Has working buttons and links
• Shows appropriate error/success messages
• Doesn't have overlapping or cut-off elements
• Is usable with keyboard navigation where applicable

6. Check Different Environments

Depending on the project, I test:

• Chrome
• Firefox
• Safari
• Desktop
• Mobile/tablet
• Different screen sizes

7. Check Related Features

A new feature shouldn't break something that already worked.

I perform regression testing around related functionality.

For example, if a new checkout feature is added, I'd also check:

• Cart
• Product pages
• Login
• Payment
• Order confirmation
• Order history

8. Test Performance & Errors

I look for:

• Slow loading
• Freezing
• Unexpected crashes
• Console errors
• Failed network requests
• Duplicate requests
• Incorrect loading states

9. Document Bugs

When I find a bug, I record enough information for a developer to reproduce it.

A good bug report includes:

Title: Login button doesn't respond after entering valid credentials

Steps to reproduce:

1. Open the login page
2. Enter a valid email
3. Enter a valid password
4. Click Log In

Expected: User is logged in and redirected to the dashboard.

Actual: Nothing happens.

Environment: Chrome / macOS

Severity: High

10. Retest Fixes

After a developer fixes a bug, I don't simply mark it resolved.

I:

1. Repeat the original steps
2. Confirm the bug is fixed
3. Test related functionality
4. Make sure the fix didn't introduce another problem

My Final QA Question

Before I consider a feature ready, I ask:

"What would a real user do that I haven't tested yet?"

That's often where the interesting bugs are hiding.