Manual Testing Notes

Manual Testing Notes
---

1. Basic Testing Concepts

Software Testing is the process of verifying that a system works as expected and is free of bugs.

SDLC (Software Development Life Cycle) defines the steps for software development, while STLC (Software Testing Life Cycle) defines the stages for testing.

Error: Human mistake, Defect: Issue in the software, Failure: When defect causes system to fail.

Verification ensures product is being built right; Validation ensures the right product is being built.



---

2. Types & Levels of Testing

Functional Testing checks what the system does; Non-functional Testing checks how it performs (like performance, security).

Smoke Testing is basic build verification; Sanity Testing checks minor fixes.

Regression Testing ensures new code doesn’t break existing features; Retesting checks a specific fix.

Levels: Unit → Integration → System → UAT (User Acceptance Testing).



---

3. Test Documentation

Test Plan: A detailed document outlining scope, approach, resources, and schedule.

Test Strategy: High-level document about testing objectives and techniques.

Test Case: Includes test steps, input data, expected result, and actual result.

RTM (Requirement Traceability Matrix) maps test cases to requirements to ensure coverage.



---

4. Defect/Bug Life Cycle

Stages: New → Assigned → Open → Fixed → Retest → Verified → Closed/Rejected.

Severity is the impact of the defect; Priority is how soon it should be fixed.

Good bug reports include: steps to reproduce, expected vs actual results, screenshots/logs.



---

5. Test Design Techniques

Equivalence Partitioning: Dividing data into valid and invalid classes.

Boundary Value Analysis (BVA): Testing values at the edges (e.g., min-1, min, max, max+1).

Decision Table Testing: Covers different input combinations.

State Transition: Testing different states and transitions in a system.

Error Guessing: Based on experience to guess where bugs might be.



---

6. Agile & Scrum Concepts

Agile: Iterative and incremental approach with fast feedback and continuous delivery.

Scrum Roles: Product Owner, Scrum Master, Development Team.

Artifacts: Product Backlog, Sprint Backlog, Increment.

Events: Sprint Planning, Daily Stand-up, Sprint Review, Sprint Retrospective.

User Stories: Requirements written from the user perspective, e.g., “As a user, I want…”



---

7. Testing Tools (Basics)

JIRA: Used for bug tracking and managing Agile projects.

TestLink/Zephyr: Tools for test case management.

Postman: Tool for API testing—sending requests and validating responses.

SQL: Used to validate backend data and ensure data integrity.



---

8. Real-Time Testing Scenarios

Login Page: Validate valid/invalid input, password masking, forgot password, etc.

E-commerce: Test search, add to cart, payment, order confirmation.

Unclear requirements: Communicate with BA/PO for clarification.

Developer rejects bug: Reproduce with clear steps and attach proof (video/log).



---

9. Testing Metrics

Test Coverage: % of requirements covered by test cases.

Defect Density: Number of defects per size (e.g., per 1,000 lines of code).

Defect Leakage: Defects missed during testing but found by end-users.

Test Execution Report: Summary of test execution status (pass/fail/block).



---

10. Interview-Specific Questions & Project Discussion

Be ready to explain your current/previous project, your role, and responsibilities.

Explain how you write and execute test cases.

Talk about tools you used (JIRA, Postman, SQL).

Discuss how you communicate with developers, handle bugs, and prioritize test cases.



---

Comments

Post a Comment

Popular posts from this blog

10 automation test cases for https://www.saucedemo.com/ (Sauce Demo)

 Here are 10 automation test cases for https://www.saucedemo.com/ (Sauce Demo), each with detailed steps and expected results . These are designed to simulate realistic user scenarios and we would be implemented using tools like Selenium, Cypress, or Playwright later. 🔹 Test Case 1: Valid Login Objective : Verify successful login with valid credentials. Steps : Navigate to https://www.saucedemo.com/ Enter Username : standard_user Enter Password : secret_sauce Click the Login button Expected Result : User is redirected to the inventory page ( /inventory.html ) with a list of products displayed. 🔹 Test Case 2: Invalid Login Objective : Validate error handling with incorrect credentials. Steps : Navigate to the login page Enter Username : invalid_user Enter Password : wrong_password Click the Login button Expected Result : Error message displayed: "Epic sadface: Username and password do not match any user in this service...
Read more

Java Roadmap for SDET Superstars!

Image
Java Roadmap for SDET Superstars! Your ultimate journey to mastering Java for test automation! Step 1: Java Basics – The Foundation Learn the grammar of Java 📚✨ 🧮 Variables & Data Types (int, float, boolean) ➕ Operators (+, -, *, /, %) 🔁 Loops (for, while, do-while) 🧠 Conditions (if-else, switch) 📦 Arrays & Strings Step 2: OOP – Think Like a Developer Become a Java ninja with Object-Oriented Programming 🐱‍👤⚔️ 🧱 Classes & Objects 🏗️ Constructors 👪 Inheritance 🎭 Polymorphism 🧬 Abstraction & Interfaces 🔐 Encapsulation Step 3: Exception Handling – Be Ready for Chaos Handle the unexpected like a pro! 🧨⚠️ try , catch , finally throw and throws 🚨 Custom Exceptions Step 4: Collections – Organize Like a Boss Work with lists, maps & sets like a data wizard 📦🪄 🗃️ List, Set, Map 🌀 ArrayList, HashMap, HashSet 🔁 Iteration (for-each, iterator) 🧠 Sorting & Filtering Step 5: Java 8+ – Modern & Cool Features Lev...
Read more

Mastering XPath in Selenium 4 🚀 – Supported Functions & Axes Explained

 Absolutely! Here's a complete list of XPath functions and axes supported by Selenium 4 (which uses XPath 1.0), with descriptions and examples . 🟢 XPath Features Supported by Selenium 4 🧭 ALL XPath Axes (13 Total) Axis Name Description ancestor:: All ancestors (parent, grandparent, etc.) of the current node ancestor-or-self:: All ancestors + the current node attribute:: All attributes of the current node (usually @attribute shorthand is used) child:: All direct children of the current node descendant:: All descendants (children, grandchildren, etc.) of the current node descendant-or-self:: All descendants + the current node following:: All nodes after the current node in the document following-sibling:: All sibling nodes after the current one namespace:: All namespace nodes of the current node (rarely used in HTML) parent:: Immediate parent of the current node preceding:: All nodes that come before the current node prece...
Read more