SDET Blueprint

  🧠 What is Database Testing? Database Testing is a type of software testing that focuses on validating the data integrity, accuracy, consistency, and performance of a database. It ensures that: Data is stored and retrieved correctly. CRUD operations (Create, Read, Update, Delete) work as expected. Business rules and constraints are enforced. The database performs well under load. It typically involves: Schema Testing (tables, keys, indexes) Data Validation (correctness of stored data) Stored Procedure & Trigger Testing Performance Testing (query response time, indexing) Security Testing (SQL injection, access control) 🛒 Real-Life Example 1: E-Commerce Platform During Holiday Sale Scenario: An e-commerce site like Amazon or Daraz experiences a surge in traffic during Black Friday. Database Testing Focus: Load Testing: Simulate thousands of concurrent users adding items to c...

  ✅ 1. Equivalence Partitioning (EP) What it is: Divides input data into partitions of equivalent data from which test cases can be derived. The idea is that if one value in a partition works, all others will too. Example: If a form accepts ages from 18 to 60: Valid partitions: 18–60 Invalid partitions: <18 and >60 Test cases: One value from each partition: 25 (valid), 17 (invalid), 61 (invalid) When to use: When input data can be grouped into ranges or categories. ✅ 2. Boundary Value Analysis (BVA) What it is: Focuses on values at the edges (boundaries) of input ranges, where defects are most likely to occur. Example: For an input field that accepts values from 1 to 100: Test boundaries: 0, 1, 2 and 99, 100, 101 Test cases: 0 (just below), 1 (lower boundary), 2 (just above) 99 (just below), 100 (upper boundary), 101 (just above) When to use: When input fields have defined minimum and maximu...

  🚀 Performance Testing Performance Testing is a type of non-functional testing that evaluates the speed, stability, scalability, and responsiveness of a software application under a specific workload. 🔹 Goals: Identify bottlenecks Ensure the system meets performance benchmarks Validate response time, throughput, and resource usage Example: Testing how fast a banking app processes 10,000 concurrent transactions. 👥 Load Testing Load Testing is a subset of performance testing that checks how a system behaves under expected or peak user loads . It simulates multiple users accessing the system simultaneously. 🔹 Purpose: Validate system performance under normal and high traffic Identify scalability limits and response delays Example: Simulating 5,000 users shopping during a flash sale on an e-commerce site. 💥 Stress Testing Stress Testing evaluates the system’s robustness and stability by pushing it...

Agile Testing is a software testing practice that follows the principles of Agile software development . Unlike traditional testing (which happens after development), Agile Testing is continuous, collaborative, and iterative —it happens alongside development in short cycles called sprints . 🔑 Key Characteristics: Continuous Testing: Testing starts from day one and continues throughout the project. Collaborative: Testers, developers, and product owners work closely together. Customer-Focused: Testing ensures the product meets real user needs , not just technical specs. Flexible & Adaptive: Test plans evolve as the product and requirements change. Shift-Left Approach: Testing is done early and often to catch issues sooner. 🧩 Agile Testing Life Cycle (Simplified) Impact Assessment: Understand user stories and acceptance criteria. Test Planning: Define what to test in the sprint. Daily St...

 The purpose of Software Quality Assurance (SQA) is to ensure that the software being developed meets the required quality standards, is free of critical defects, and performs reliably and securely in real-world conditions. It is a proactive, process-oriented discipline that works in parallel with software development to prevent issues before they occur. 🎯 Primary Purposes of SQA 1. Ensure Software Quality Verifies that the product meets functional and non-functional requirements . Ensures reliability, usability, performance, and security . 2. Prevent Defects Early Focuses on process improvement to catch issues before they become costly bugs. Encourages early reviews, audits, and static analysis . 3. Ensure Compliance with Standards Enforces adherence to industry standards like ISO, IEEE, or CMMI. Ensures that coding practices, documentation, and testing follow best practices. 4. Reduce Cost and Tim...

  There are some unique terms in software testing. Such as: Defect Clustering, Pesticide Paradox, Absence of Error Fallacy, Defect Cascading and more. So, Let's study about the concepts. 🧠 Advanced Testing Principles & Fallacies 🧩 Term 📘 Description Defect Clustering Most defects are found in a small number of modules (Pareto Principle). Pesticide Paradox Repeating the same tests will no longer find new bugs—tests must evolve. Absence of Error Fallacy A bug-free system may still fail if it doesn’t meet user needs. Defect Cascading One defect triggers others in dependent modules, causing a chain reaction. Confirmation Bias in Testing Tendency to write tests that confirm the system works, not that it fails. Test Oracle Problem Difficulty in determining the correct expected outcome for a test. ...

  🧪  1–5: Quality & Risk Management How would you handle a situation where you discover a critical bug just before a major release? I would immediately assess the severity and impact of the bug, document it thoroughly, and escalate it to the product owner and release manager. I’d facilitate a quick risk analysis meeting with stakeholders to decide whether to delay the release, deploy a workaround, or proceed with a known issue. My priority is always user trust and product stability.  How would you handle testing a feature with vague or incomplete requirements? I’d initiate a clarification session with the product owner or BA. Meanwhile, I’d use exploratory testing to uncover edge cases and document assumptions. I’d also maintain a list of open questions and update test cases as clarity improves. How would you handle a scenario where a developer insists a bug is not valid, but you beli...

  Here’s the key difference between “In Scope” and “Out of Scope” when writing a test plan—or any project plan: 🔍 In Scope This defines what the team will work on or test . It includes: Features to be tested (e.g., login, checkout) Supported platforms (e.g., mobile, desktop) Types of testing (e.g., functional, security, UI) Expected deliverables Think of it as the “YES” list—things you’re promising to cover. 🚫 Out of Scope This outlines what the team won’t work on or test , either because: It’s not relevant to current goals It’s being handled by another team It might be deferred to a future phase Scope Clarification ✅ In Scope The following items are included in the testing efforts: User functionalities such as registration, login, product search, and checkout Payment gateways : testing with credit/debit cards and digital wallets Notifications via email and SMS ...