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

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

🚀 UI vs. UX Testing: What QA Testers Should Know

  🚀 UI vs. UX Testing: What QA Testers Should Know Introduction User satisfaction is the cornerstone of any successful application. While functionality is crucial, how an app looks and feels can make or break the user experience. This is where UI (User Interface) testing and UX (User Experience) testing come into play. Both are essential for ensuring that an application is not only functional but also user-friendly and visually appealing. However, these two types of testing serve different purposes and require different approaches. In this article, we will explore UI vs. UX testing , their differences, their significance in quality assurance (QA), and how testers can effectively carry out both. What is UI Testing? Definition User Interface (UI) testing focuses on verifying the graphical interface of an application to ensure that all UI components function correctly and meet design specifications. It examines elements like buttons, forms, fonts, colors, menus, and images ...
Post a Comment
Read more

4th Part 100 Glassdoor QA interview reviews

  🧪 Section 1: Manual Testing Fundamentals (1–20) What is the difference between verification and validation? Verification ensures the product is built correctly. Validation checks if the right product is built. What are the different levels of testing? Unit testing, integration testing, system testing, and acceptance testing. Define a test case and test scenario. A test case is a set of inputs and steps to verify a function. A test scenario is a high-level idea of what to test. What is severity and priority in bug tracking? Severity reflects the impact. Priority reflects the urgency to fix. What is black-box testing? Testing without knowing internal code logic; based on inputs and outputs. What is exploratory testing? Unstructured testing to explore the application freely. What is functional vs. non-functional testing? Functional testing checks business logic. Non-functional checks performance, scalability, etc. What is regression testing? Retesting features to ensure changes hav...
Post a Comment
Read more