Skip to main content

🚀 Day 1 of 100 Days of QA Learning!


I'm kicking off this 100-day journey to dive deep into Quality Assurance (QA) and help others learn along the way! 🎯
For today's post, I covered the QA job roles, types of testing, and a quick-start guide for manual testing—all structured for easy learning within an hour! ⏳
My learning partners ChatGPT for research and Canva to design the visuals, making this an engaging and insightful learning experience.

🔍 Check out the details below, and let's grow together in our QA journey! 💡 


Job Titles You Can Apply For in QA:

  • Quality Assurance (QA) Engineer
  • Software Tester
  • QA Analyst
  • Test Automation Engineer
  • Performance Tester
  • QA Lead
  • QA Manager
  • SDET (Software Development Engineer in Test)

There are many types of software testing, but they generally fall into two main categories:

1. Functional Testing

This type of testing verifies that the application works as expected based on requirements.

  • Unit Testing – Tests individual components or functions.

  • Integration Testing – Ensures that different modules work together.

  • System Testing – Tests the complete system as a whole.

  • User Acceptance Testing (UAT) – Checks if the system meets business requirements before release.

  • Regression Testing – Ensures that new changes don’t break existing functionality.

  • Smoke Testing – A quick test to check if the basic functionality works.

  • Sanity Testing – Focuses on specific fixes or changes to verify they work as intended.

2. Non-Functional Testing

This type of testing evaluates aspects like performance, security, and usability.

  • Performance Testing – Measures speed, scalability, and responsiveness.

    • Load Testing – Tests system behavior under normal and peak loads.

    • Stress Testing – Checks the system’s breaking point.

    • Soak Testing – Runs the system for an extended period to detect memory leaks or degradation.

  • Security Testing – Identifies vulnerabilities and ensures data protection.

  • Usability Testing – Ensures the application is user-friendly.

  • Compatibility Testing – Checks if the application works on different devices, OS, and browsers.

  • Accessibility Testing – Ensures the software is usable by people with disabilities.

Quick Manual Testing Guide 🛠️

1️⃣ Understanding Requirements

  • Read and analyze the project requirements, user stories, or specifications.

  • Identify test scenarios and edge cases.

2️⃣ Test Planning

  • Define the scope, test objectives, and types of tests (e.g., functional, UI, regression).

  • Prepare test cases, checklists, or test charters.

3️⃣ Test Execution

  • Execute test cases manually.

  • Validate expected vs. actual results.

  • Take screenshots or screen recordings for evidence.

4️⃣ Defect Reporting

  • Document bugs with clear steps to reproduce.

  • Provide screenshots, logs, or videos.

  • Assign severity and priority.

5️⃣ Regression Testing

  • Retest fixed defects.

  • Ensure new changes don’t break existing functionality.

6️⃣ Exploratory Testing

  • Think like an end-user and explore the application beyond predefined test cases.

  • Look for usability, UI inconsistencies, and hidden defects.

7️⃣ Test Closure

  • Summarize test results.

  • Share findings with the team.

  • Suggest improvements for future releases.


Comments

Post a Comment

Popular posts from this blog

Understanding XML for QA Testing

 As a QA tester, working with XML is essential, especially for API testing, data validation, and automation . Today, I explored the key concepts every QA should know about XML. 🔹 What is XML? XML ( eXtensible Markup Language ) is used for storing and transporting data in a structured format. It’s widely used in APIs (SOAP), test data, and configurations . 🔹 Why QA Testers Should Learn XML? ✅ API Testing – SOAP APIs use XML for requests & responses. ✅ Test Data Handling – XML is used in test scripts, Selenium, and data-driven testing. ✅ Config Files – Many automation tools (TestNG, Jenkins) use XML for setup. 🔹 Key XML Concepts for QA 📌 XML Structure – Elements, attributes, nesting, and schema validation. 📌 XPath – Used for locating XML nodes in automation & API testing. 📌 XML Schema (XSD) – Ensures data correctness in APIs. 📌 Parsing XML – Reading & extracting values using tools like Postman, Python, or Java . 💡 Where to Learn XML? 📖 W3Scho...
Post a Comment
Read more

30 Manual Testing interview questions from glass door

Here are 30 manual testing interview questions commonly encountered in interviews, compiled from various sources including Glassdoor: What is the difference between Quality Assurance (QA), Quality Control (QC), and Software Testing? QA focuses on improving the processes to deliver Quality Products. QC involves the activities that ensure the verification of a developed product. Software Testing is the process of evaluating a system to identify any gaps, errors, or missing requirements. Can you explain the Software Testing Life Cycle (STLC)? The STLC includes phases such as Requirement Analysis, Test Planning, Test Case Development, Environment Setup, Test Execution, and Test Closure. What is the difference between Smoke Testing and Sanity Testing? Smoke Testing is a preliminary test to check the basic functionality of the application. Sanity Testing is a subset of regression testing to verify that a specific section of the application is still worki...
Post a Comment
Read more

QA Automation journey

🔥 50-Day QA Automation Learning Plan (TS + Playwright) Day Topic Focus 🔹 Phase 1: Foundations (Days 1–10) | 1 | Introduction to Test Automation & Testing Pyramid | What, why, and how of automation | | 2 | Intro to JavaScript & TypeScript | Setup, syntax overview | | 3 | Variables, Data Types, Constants | Hands-on coding | | 4 | Functions, Loops, Conditionals | Practice basic logic | | 5 | Classes & Constructors in TS | OOP basics | | 6 | Setup Playwright Project | Install, basic structure | | 7 | First Test with Playwright | Run test, understand selectors | | 8 | Debugging in Playwright | Logs, retries, timeout handling | | 9 | Folder Structure & Best Practices | Test organization | | 10 | Recap & Mini Project | Small Playwright test project | 🔹 Phase 2: Unit & API Testing (Days 11–25) | 11 | What is Unit Testing? | Concept + console app example | | 12 | Annotations & Test Hooks | beforeAll, afterEach, etc. | | 13 | Parametrized...
Post a Comment
Read more