Skip to main content

8 Core Testing Types Every Manual Tester Should Know - DAY 1

 

8 Core Testing Types Every Manual Tester Should Know-- 

Introduction
As a QA Engineer at Codenia Technologies, I’ve learned that choosing the right testing type is like picking the right tool for a job. Miss a step, and bugs slip through. Here are 8 essential testing types every manual tester needs, with practical tips and examples to make you a bug-hunting pro!

1. Smoke Testing: The First Checkpoint

  • What: Quick tests to check if a build is stable enough for deeper testing.
  • When: After a new build deployment.
  • Example: In an e-commerce app, I tested login, search, and checkout to ensure they didn’t crash. Found a broken search button—build rejected!
  • Tip: Use a 10-minute checklist in JIRA to cover key features.

2. Sanity Testing: Verify the Fix

  • What: Focused tests to confirm specific fixes or changes work.
  • When: After a bug fix or minor update.
  • Example: A payment bug was fixed; I tested only the payment flow to confirm it worked.
  • Tip: Limit to 5–10 test cases to save time.

3. Functional Testing: Features That Deliver

  • What: Test each feature against requirements.
  • When: During core testing phases.
  • Example: For a login page, I tested valid/invalid credentials, password recovery, and UI elements. Caught a “forgot password” glitch!
  • Tip: Use a requirements traceability matrix (RTM) in Excel.

4. Regression Testing: Protect the Past

  • What: Ensure new changes don’t break existing features.
  • When: After updates or new features.
  • Example: After adding a coupon feature, I retested checkout to confirm no impact. Found a discount miscalculation bug!
  • Tip: Automate repetitive cases with tools like Selenium if possible.

5. Integration Testing: Modules in Harmony

  • What: Test interactions between modules.
  • When: After individual modules are tested.
  • Example: Tested API integration between cart and payment gateway—caught a data mismatch.
  • Tip: Use Postman for API testing.

6. System Testing: The Big Picture

  • What: End-to-end testing of the entire application.
  • When: After integration testing.
  • Example: Tested a travel app’s full flow: search → book → payment → confirmation. Found a timeout error.
  • Tip: Map user journeys in Trello for clarity.

7. User Acceptance Testing (UAT): The User’s Voice

  • What: Validate the app from a user’s perspective.
  • When: Before production release.
  • Example: Asked beta users to test a banking app’s UI—caught a confusing button label.
  • Tip: Use Google Forms to collect user feedback.

8. Exploratory Testing: Unleash Your Curiosity

  • What: Freestyle testing to find unexpected bugs.
  • When: When time allows or scripts miss edge cases.
  • Example: While exploring a chat app, I spammed messages and crashed the server—critical bug!
  • Tip: Use Bug Magnet (Chrome extension) for quick test ideas.


Conclusion
Mastering these 8 testing types will make you a versatile QA who catches bugs before they reach users. Start by applying one type to your next project, and share your results! What’s your favorite testing type? Comment below and join the #QAFamily!



Comments

Post a Comment

Popular posts from this blog

No, AI Won't Steal Your Job: Why Manual Testing is More Critical Than Ever

"Manual Testing Isn't Dead. It's Your Secret Weapon for Quality." If you spend any time on tech forums or LinkedIn, you’ve heard the prophecy: “Automation and AI are coming to replace manual testers.” The story goes that in the near future, smart algorithms will handle everything, making human testers obsolete. I’m a Software QA Engineer who has been in the trenches with everything from complex fintech platforms to social media and gaming apps. And I’m here to tell you that this prediction is fundamentally wrong. Manual testing isn't dead. It's evolving. And in an age dominated by automation, its role has become more specialized and more critical than ever. Automation can check for expected outcomes, but it can't replicate the one thing that truly defines quality: the human experience. The Automation Fallacy: What a Script Can't See Test automation is a game-changer, and I rely on it every day. It's brilliant for running repetitive regression suite...
Post a Comment
Read more

🌟 The Future of QA in 2025: Why Testers Are the Superheroes of Tech

  🚀 Introduction Developers get the spotlight. AI steals the headlines. But here’s the truth no one tells you: without testers, everything breaks . Think about it. Banking apps that lose your money. Healthcare systems that give wrong reports. Flight booking portals that crash mid-payment. One missed bug can cost millions — and sometimes even lives. That’s why 2025 is not the end of QA . It’s the beginning of a new era where testers become the superheroes of software development . 🦸 Testers: The Last Line of Defense In every software team, roles are clear: Developers build features. Testers protect users. And in today’s world, protection = trust . Companies spend billions building features, but a single bug can: Destroy customer trust. Damage brand reputation. Trigger lawsuits and losses. Testers are not bug hunters. Testers are business protectors . That’s why testers are more critical than ever. 🤖 AI Won’t Replace Testers — It Will ...
Post a Comment
Read more

Top 10 Manual Test Cases for Login Page (With Examples)

 The login page is the gateway to any application. As a QA tester, validating this feature is critical. In this post, we’ll cover 10 essential manual test cases you must write for login functionality, along with examples. Test Cases: Test Case ID Test Scenario Expected Result TC01 Enter valid username and password User logs in successfully TC02 Leave both fields blank and click login Show “Fields cannot be empty” TC03 Enter wrong username and correct password Show “Invalid credentials” TC04 Enter correct username and wrong password Show “Invalid credentials” TC05 Check password masking Password should be hidden with dots TC06 Check "Remember Me" functionality User stays logged in after refresh TC07 Click on "Forgot Password" Redirects to password recovery page TC08 Enter SQL injection script Input should be sanitized TC09 Enter special characters in username Show input validation TC10 Test login with expired credentials Show “Account expired” Bonus Tips: Al...
Post a Comment
Read more