Complete Manual Testing Guide:
Zero to Senior QA Lead

📌 Fundamentals & Core Concepts

1. What is the difference between Verification and Validation?

English: Verification is checking the documents and design (Static Testing), while Validation is checking the actual product by executing code (Dynamic Testing).
Hinglish: Verification me documents aur design check karte hain, aur Validation me actual software run karke check karte hain.

2. Explain the STLC (Software Testing Life Cycle) phases.

English: The phases of STLC include:

• Requirement Analysis
• Test Planning
• Test Case Development
• Environment Setup
• Test Execution
• Test Closure

Hinglish: STLC me requirements analyze karne se lekar bug reporting aur closing tak ke saare steps aate hain.

3. What is a Bug Life Cycle?

English: A bug goes through several stages: New → Assigned → Open → Fixed → Retest → Closed (or Reopened/Deferred).
Hinglish: Bug report hone se target fix hone tak ke status change ko Bug Life Cycle kehte hain.

4. White Box vs Black Box Testing?

English:
White Box: Focuses on internal code structure (done by developers).
Black Box: Focuses on external functionality based on requirements (done by testers).
Hinglish: White box me code dekhte hain, black box me sirf features check karte hain.

5. What is Boundary Value Analysis (BVA)?

English: BVA is a test design technique where testing is performed at the boundaries (edges) of the input ranges (e.g. 1-100 range → test 0, 1, 2, 99, 100, 101).
Hinglish: BVA me range ke corners ya edges check karte hain (jaise 1-100 range me 1 aur 100).

6. Positive vs Negative Testing?

English: Positive testing checks if the system works with valid data, while Negative testing checks if it correctly handles invalid data.
Hinglish: Sahi data ke saath test karna Positive hai, aur galat data daal kar check karna Negative testing hai.

7. What is RTM (Requirement Traceability Matrix)?

English: A document that maps requirements with test cases to ensure that all requirements are covered by testing.
Hinglish: Requirement aur test cases ko match karne wala document taaki koi feature miss na ho.

8. Exploratory vs Scripted Testing?

English: Exploratory testing is simultaneous learning and testing without a pre-written script, while Scripted testing follows predefined test cases.
Hinglish: Exploratory me bina kisi script ke software explore karke test karte hain.

9. Have you worked in Agile methodology?

English:
Yes, I have worked in Agile methodology where work is done in short sprints with continuous development, testing, and feedback. I participate in sprint planning, daily standups, and sprint reviews to ensure timely and quality delivery.

Agile Sprint Cycle:

1. Planning
2. Develop
3. Test
4. Deploy
5. Review

Hinglish: Yes, maine Agile methodology me kaam kiya hai jahan kaam chhote sprints me hota hai aur development, testing aur feedback continuously chalta rehta hai.

10. Explain the points you consider while writing a good test case.

English:

• Test case should be clear and simple
• Must include pre-conditions and post-conditions
• Should cover both positive and negative scenarios
• Should be reusable and easy to maintain
• Must have a proper expected result
• Use unique test case IDs for tracking

Hinglish:

• Test case clear aur simple hona chahiye
• Pre-conditions aur post-conditions mention hone chahiye
• Positive aur negative dono scenarios cover hone chahiye
• Test case reusable aur easy to maintain hona chahiye
• Proper expected result likhna zaroori hai
• Tracking ke liye unique test case ID use karni chahiye

11. What is the Bug Life Cycle? (Detailed)

English: The Bug Life Cycle is the different stages a bug goes through from the time it is found until it is fixed and closed. It helps to track the status of a defect properly.

Steps of Bug Life Cycle:

• New: Bug found and logged.
• Assigned: Assigned to a developer.
• Open: Developer starts working.
• Fixed: Developer fixes the issue.
• Retest: Tester retests the bug.
• Closed: If working fine, the bug is closed.
• Reopen: If still failing, it is reopened.
• Deferred / Rejected: If not valid or postponed for later.

Hinglish: Bug Life Cycle wo stages hote hain jisme ek bug, find hone se lekar fix aur close hone tak jata hai.

12. Test Scenario vs Test Case (Detailed)

Test Scenario:

• High-level idea of what to test.
• Describes what to test (e.g., Login).
• Covers one feature.
• Simple language, no detailed steps.

Test Case:

• Detailed step-by-step instructions.
• Describes how to test.
• Includes steps, inputs, and expected results.
• Actual tool for testing.

Hinglish: Scenario matlab kya test karna hai, aur Test Case matlab kaise (detailed steps) test karna hai.

13. Functional vs Non-Functional Testing

English:
Functional Testing: Checks what the system does (Features, Login, Add to Cart).
Non-Functional Testing: Checks how the system performs (Speed, Load, Security, UI).
Hinglish: Functional testing features check karti hai; Non-Functional testing performance aur security check karti hai.

14. What is STLC in software testing? (Detailed Phases)

English: Software Testing Life Cycle (STLC) is a step-by-step process followed by testers to plan and execute testing activities.

Phases: Requirement Analysis → Test Planning → Test Case Design → Test Environment Setup → Test Execution → Defect Reporting → Test Closure.
Hinglish: STLC ek process hai jisme tester planning se lekar testing aur closure tak kaam karta hai.

15. What is a Software Testing Model? (V-Model, Waterfall, Agile)

English: A process or approach followed to test software in a structured way.

Common Models:

• V-Model: Testing runs parallel with development.
• Waterfall Model: Sequential process (Requirement → Design → Coding → Testing).
• Agile Model: Iterative and sprint-based testing.
The Agile Scrum Sprint Lifecycle

Hinglish: Software Testing Model batata hai ki development ke dauran testing ka approach kya hoga.

16. What are the 7 Principles of Software Testing?

1. Testing shows presence of defects: Testing bugs dhoondh sakti hai, par ye prove nahi karti ki software 100% bug-free hai.
2. Exhaustive testing is not possible: Har cheez test karna impossible hai.
3. Early testing saves time & cost: Requirement stage se start karne par cost kam aati hai.
4. Defect clustering: Zyada bugs kuch specific modules me hi milte hain.
5. Pesticide paradox: Same tests baar-baar chalane se naye bugs nahi milte.
6. Testing depends on context: Mobile app vs Medical app testing alag hoti hai.
7. Absence-of-errors fallacy: Bug-free hona kafi nahi hai agar software user ke liye useful na ho.

Hinglish: Ye 7 rules hain jo tester ko effective testing karne me guide karte hain.

17. What is Severity and Priority in Software Testing?

English:
Severity: How much the defect affects the system internally (Technical impact).
Priority: How fast the defect should be fixed from a business perspective.

Examples Matrix:

Scenario	Severity	Priority
App crashes on clicking Login	High	High
Logo spelling mistake on homepage	Low	High
App crashes on a rarely used hidden page	High	Low
Small color mismatch on a button	Low	Low

18. Difference between Smoke and Sanity Testing?

English:
Smoke Testing: A basic check to verify that the application is stable and the build is ready for further testing (build verification).
Sanity Testing: A narrow and deep check to confirm that new functionality or a bug fix is working properly.

Feature	Smoke Testing	Sanity Testing
When is it done?	On Initial build	After minor changes/fixes
Depth of Test	Shallow & Wide	Narrow & Deep
Objective	Verify application stability	Verify rationality of a feature

Hinglish: Smoke Testing build stability check karta hai; Sanity Testing naye badlav (changes) ko verify karta hai.

19. What is Regression Testing?

English: Regression Testing is done to make sure that new changes, bug fixes, or new features have not affected the existing functionality of the application.
Hinglish: Regression Testing ye ensure karta hai ki naye changes ke baad purane features sahi se kaam kar rahe hain.

20. How do you ensure complete test coverage?

English: By writing test cases based on requirements and user stories, covering both positive and negative scenarios. I also use a Traceability Matrix (RTM).
Hinglish: Requirements ke base par detailed test cases likhkar aur RTM use karke main complete coverage ensure karta hoon.

21. Verification vs Validation?

English:
Verification (Static): Are we building the product right? (Checking documents, design, code).
Validation (Dynamic): Are we building the right product? (Testing the actual software).
Hinglish: Verification check karta hai ki process sahi hai; Validation actual app chala kar check karta hai.

22. What are BVA and Equivalence Partitioning?

English: Both are Black Box Test Design Techniques to reduce the number of test cases.

Technique	Invalid Test	Valid Test	Invalid Test
Equivalence	< 18 (e.g., 10)	18 ≤ Age ≤ 60	> 60 (e.g., 75)
Boundary (BVA)	17	18, 19, 59, 60	61

Hinglish: Ye methods test cases kam karne aur bugs dhoondhne me help karte hain partitions aur edges ke through.

23. What is Testing Life Cycle (STLC)?

English: STLC is the sequence of activities performed during testing: Requirement Analysis → Test Planning → Test Case Design → Test Execution → Test Closure.
Hinglish: STLC testing ka pura timeline hai, planning se lekar report close karne tak.

24. What is Integration Testing?

English: Integration testing verifies interaction between different modules after unit testing.
Hinglish: Jab do ya zada modules ko mila kar check karte hain toh use Integration testing kehte hain.

25. What is Load Testing?

English: Load testing checks how the application behaves under expected user load.
Hinglish: Application par expected users ka load daal kar uska performance check karna.

26. How many test cases will you write per day?

English: It depends on the module complexity. For simple modules: 20–25 cases. For complex modules: 10–15 cases.
Hinglish: Complexity ke hisab se 10 se 25 tak likh sakte hain ek din me.

27. Where do you maintain the test case?

English: Test cases are maintained in tools like TestRail, JIRA, or Excel sheets.
Hinglish: Hum test cases TestRail, JIRA ya normal Excel sheet me rakhte hain.

28. What is Priority in bug reporting?

English: Priority means how fast a bug should be fixed. High (Critical), Medium (Normal), Low (Minor).
Hinglish: Priority batati hai ki developer ko bug kitni jaldi fix karna chahiye.

29. Roles of each team member (Agile/QA)?

English:
Developer: Writes code. Tester: Tests application. BA: Gives requirements. Scrum Master: Manages Agile process. Product Owner: Decides features.
Hinglish: Developer code likhta hai, Tester check karta hai, BA requirements deta hai, aur PO features decide karta hai.

30. What are Agile Ceremonies?

English: Agile ceremonies are periodic meetings in Agile: Sprint Planning, Daily Standup, Sprint Review, and Sprint Retrospective.
Hinglish: Agile me project cycle ke meetings ko ceremonies bolte hain: Planning, Daily meeting, Review, aur Retrospective.

31. How do you maintain test cases?

English: Test cases are maintained in tools like TestRail, JIRA (with Xray or Zephyr), or shared Excel sheets.
Hinglish: Test cases hum TestRail, JIRA ya Excel sheet me properly maintain karte hain.

32. How many test cases can you write per day?

English: On average, 15-25 test cases per day, depending on the complexity of the feature and clarity of requirements.
Hinglish: Module ke complexity par depend karta hai, usually 15 se 25 test cases likh sakte hain.

33. What is Priority and how do you rate it?

English: Priority defines the urgency of fixing a bug. It is typically rated as High (fix immediately), Medium (fix in next release), or Low (fix later).
Hinglish: Priority batati hai bug kitni jaldi fix hona chahiye (Urgency).

🚀 Deep Dive: SDLC vs STLC Frameworks

🏢 Practical Project Scenario: Testing an E-commerce Login

📌 Detailed Q&A Repository

1. What is Software Testing?

English: The process of evaluating a software product to identify defects.
Hinglish: Software mein galtiyan dhoondhne ka process.
Example: Clicking all buttons to see if they work.

2. What is a 'Bug'?

English: A deviation from expected behavior in a software application.
Hinglish: Jab software waisa kaam na kare jaisa usse karna chahiye.
Example: Login button not working.

3. What is SDLC?

English: A framework defining tasks performed at each step in the software development process.
Hinglish: Software banane ka pura process, step-by-step.
Example: Requirements -> Design -> Coding -> Testing -> Deployment.

4. What is STLC?

English: A sequence of specific activities performed during the testing process.
Hinglish: Testing karne ka pura process, step-by-step.
Example: Requirement Analysis -> Test Planning -> Test Execution.

5. What is a Test Case?

English: A detailed set of steps to test a specific functionality.
Hinglish: Kisi feature ko test karne ke liye step-by-step instructions.
Example: Steps to login: 1. Open URL, 2. Enter username, 3. Enter password, 4. Click Login.

6. What is Internationalization (I18N)?

English: Designing a software application so that it can be adapted to various languages and regions without engineering changes.
Hinglish: Product ko aise design karna ki wo kisi bhi language mein support ho sake.
Example: Using Unicode (UTF-8) for all text.

7. What is Localization (L10N)?

English: The process of adapting an internationalized software for a specific region or language by adding local-specific components and translating text.
Hinglish: Kisi khas area ya language ke hisab se software ko dhalna (jaise translation).

8. Define Gray Box Testing.

English: Testing with partial knowledge of internal logic or database structures.
Hinglish: Jab tester ko code aur functionality dono ki thodi knowledge ho.
Example: Checking if a form saves to the specific DB table.

9. What is Monkey Testing?

English: Unpredictable inputs used to check if the app can handle random user behavior.
Hinglish: Bina kisi plan ke random clicks/data se system check karna.
Example: Rapidly clicking buttons on a slow device.

10. What is Ad-hoc Testing?

English: Informal testing performed without following any test cases or requirement docs.
Hinglish: Bina kisi document ke apni samajh se app ko check karna.
Example: Randomly trying site features during a break.

11. What is Sanity Testing?

English: Narrow focus on a specific functionality to ensure it works after changes.
Hinglish: Bugs fix hone ke baad kisi khas feature ki basic health check.
Example: Checking Logout button after Header update.

12. What is Smoke Testing?

English: Verifies basic stability (e.g., Can it launch? Can we login?) before deep testing.
Hinglish: Build aate hi basic stability (Login/Home) check karna.
Example: Checking if app opens properly on a new build.

13. Name a Functional Testing type.

English: Testing the 'what' of the software (features, inputs, outputs).
Hinglish: App ke features (Kya kaam ho raha hai) ko check karna.
Example: Testing 'Add to Cart' button.

14. What is a 'Defect'?

English: A flaw found by testers before the product goes live.
Hinglish: Jab result waisa na aaye jaisa documents mein manga tha.
Example: Expected 'Success' but got 'Error 500'.

15. What is an 'Error' in testing?

English: A human action that produces an incorrect result (e.g., typo in code).
Hinglish: Coder ya tester ki insani galti jo baad mein bug banti hai.
Example: Typing '==' instead of '===' in Javascript.

16. What is Regression Testing?

English: Ensuring that recent code changes haven't broken existing features.
Hinglish: Jo bug report kiya tha, uske fix hone ke baad dobara check karna.
Example: Tester re-verifying Bug ID 101.

17. What is Static Testing?

English: Testing without executing the code (Verification).
Hinglish: Bina app chalaye requirements aur code review karna.
Example: Reading Requirement Docs to find gaps.

18. What is Positive Testing?

English: Testing with inputs that are expected to work correctly.
Hinglish: Sahi data daal kar check karna ki system kaam kar raha hai.
Example: Logging in with correct username/password.

19. What is 'End-to-End' (E2E) testing?

English: Ensures the whole system works together (e.g., login to checkout).
Hinglish: Pura system shuru se anth tak check karna.
Example: User login -> Search -> Buy -> Logout.

20. What is Negative Testing?

English: Testing with incorrect inputs to ensure the system handles errors.
Hinglish: Galat data daal kar check karna ki error message aata hai ya nahi.
Example: Entering 'abc' in a Moble Number field.

21. What is the primary goal of UAT?

English: User Acceptance Testing ensures the tool is fit for business use.
Hinglish: UAT check karta hai ki product client ki requirements poori karta hai.
Example: Client testing the app before final handover.

22. Define 'Hotfix'.

English: A high-priority fix for a production issue.
Hinglish: Live software mein aayi badi galti ko turant theek karna.
Example: Fixing a checkout crash on a live site.

23. What is 'Latent' bug?

English: A bug that hasn't been found yet because the feature or conditions weren't met.
Hinglish: Aisa bug jo chhupa hua hai aur kisi khas vajah se hi dikhta hai.
Example: Bug that appears only on February 29th.

24. Verification vs Validation simplified?

English: Verification checks process/docs; Validation checks the final software.
Hinglish: Verification: Kya hum sahi process follow kar rahe? Validation: Kya client ki zaroorat poori hui?
Example: Reviewing specs vs Running the login.

25. What is the status 'Deferred' in Bug Life Cycle?

English: A bug that is acknowledged but scheduled for a later release.
Hinglish: Bug hai par ise agle version mein theek kiya jayega.
Example: Small spelling error deferred to v2.0.

26. What is 'Spike' in Agile?

English: A task focused on research or prototyping rather than coding a feature.
Hinglish: Kisi nayi cheez ko samajhne ke liye kiya gaya research task.
Example: Prototype for new payment gateway.

27. What is 'Traceability'?

English: The ability to track requirements through design to testing.
Hinglish: Pata lagana ki har requirement test case se judi hai ya nahi.
Example: RTM document.

28. What is 'Equivalence Class Partitioning'?

English: Focuses on testing one value from each group of inputs that behave same.
Hinglish: Inputs ko un groups mein baantna jo same result dete hon.
Example: Testing age 30 for 18-60 range.

29. Define 'Acceptance Criteria'.

English: Set of conditions that a software product must meet to be accepted by a customer.
Hinglish: Woh conditions jo poori hone par client software ko accept karega.
Example: User must be able to login within 2 seconds.

30. What is 'Crash'?

English: An unexpected termination of a software program.
Hinglish: Jab software chalte-chalte bina kisi warning ke band ho jaye.
Example: App closing when clicking on Profile.

📌 Process & Methodologies (Intermediate Level)

31. What is Boundary Value Analysis (BVA)?

English: Testing values at the boundaries of equivalence classes (e.g., 0, 1, 100).
Hinglish: Inputs ki boundaries (kinaron) pe test karna (like -1, 0, 1).
Example: If age is 1-100, test 0, 1, 100, 101.

32. What is Equivalence Partitioning?

English: Dividing input data into classes where one value represents the class.
Hinglish: Inputs ko groups mein baantna jo same result dein.
Example: Testing one value (e.g., 25) for age group 18-60.

33. What is an RTM (Requirement Traceability Matrix)?

English: Ensures every requirement has at least one associated test case.
Hinglish: Requirement ko Test Case ke saath map karna taaki kuch miss na ho.
Example: Requirement 1.0 is covered by TC_01.

34. What is Exploratory Testing?

English: Testing on the fly based on experience and intuition.
Hinglish: Bina fixed steps ke apni samajh se app ko explore aur test karna.
Example: Tester randomly trying scenarios to find complex bugs.

35. Define Test Scenario vs Test Case.

English: Scenario is high-level; Test Case is detailed with steps.
Hinglish: Scenario matlab kya test karna hai, Case matlab kaise (steps).
Example: Scenario: Forget Password; Case: Enter email, click link...

36. What is the Pesticide Paradox?

English: Tests lose effectiveness over time and need regular updates.
Hinglish: Ek hi tests baar-baar chalane se naye bugs nahi milte.
Example: Updating the regression suite every sprint.

37. What is a 'Critical' bug?

English: A major functionality is blocked and there is no alternative.
Hinglish: Jab koi main feature bilkul kaam na kare aur koi rasta na ho.
Example: Sign-up button not doing anything.

38. What is a Test Plan?

English: A document describing the scope, approach, resources, and schedule of testing activities.
Hinglish: Testing kaise hogi, kya test hoga, kaun karega, kab tak hoga - sab batane wala document.
Example: A document detailing the strategy for testing a new mobile app.

39. What is a Test Stub?

English: A dummy program that integrates with the module under test and provides the same output as the actual module.
Hinglish: Ek chhota sa nakli program jo asli module ki tarah kaam karta hai, jab asli module ready na ho.
Example: A stub for a payment gateway that always returns 'success'.

40. What is a Test Driver?

English: A program that calls the module under test, passes test data, and prints results.
Hinglish: Ek program jo asli module ko chalata hai aur usko data dekar check karna hai.
Example: A main method calling a utility function with various inputs.

41. Define 'Quality Assurance' vs 'Quality Control'.

English: QA prevents defects; QC identifies them in the final product.
Hinglish: QA bugs aane se rokta hai, QC unhe check karke dhoondhta hai.
Example: Process audits (QA) vs Running tests (QC).

42. What is 'Exhaustive Testing'?

English: Practically impossible but theoretically testing everything.
Hinglish: Har possible value aur condition ko test karna (jo mushkil hai).
Example: Testing millions of password combinations.

43. What is 'Alpha' vs 'Beta' testing?

English: Alpha is done at developer site; Beta is done at client site/real environment.
Hinglish: Alpha office mein hota hai, Beta asli users ke saath bahar.
Example: Gmail Beta (years ago).

44. What is 'Compatibility' testing?

English: Ensures the app looks and works same across Chrome, Safari, etc.
Hinglish: Alag browsers/mobile phones par app chalana.
Example: Checking site layout on iPhone vs Android.

45. What is 'Backlog' in Agile?

English: A list of everything that's known to be needed in the product.
Hinglish: Un kamo ki list jo team ko aage karne hain.
Example: User stories for the next 3 sprints.

46. What is a 'Sprint'?

English: A core unit of development in Scrum, typically 2-4 weeks.
Hinglish: Ek nichit samay (usually 2-4 hafte) jisme kaam deliver karna hota hai.
Example: Sprint 5: Implementing Login & Logout.

47. Define 'Daily Stand-up'.

English: Short (15-min) sync meeting for the team to discuss progress and blockers.
Hinglish: Rozana ki 15-minute ki meeting kaam update karne ke liye.
Example: What did I do yesterday? What will I do today?

48. What is 'Burn-down Chart'?

English: Visual tool to track sprint progress showing work remaining vs time.
Hinglish: Ye dekhne ka chart ki sprint mein kitna kaam bacha hai.
Example: Line going down as tasks complete.

49. Define 'Definition of Done' (DoD).

English: A shared understanding of what it means for work to be complete.
Hinglish: Kaam pura kab mana jayega, uska shared criteria.
Example: Code reviewed, Unit tested, and QA passed.

50. What is 'Happy Path' testing?

English: Testing the most common, error-free path through an app.
Hinglish: Sabse aasan aur bina error wala flow check karna.
Example: User login -> Search -> Buy -> Success.

51. What is Regression Testing?

English:
Regression testing means checking that old features still work correctly after new changes or bug fixes. It is important because new changes can break existing functionality.

Example: If a password reset bug is fixed, you should also test login again to make sure it still works.
Easy Line: "Re-testing old features after changes = Regression Testing"

Hinglish:
Regression testing ka matlab hai check karna ki new changes ya bug fix ke baad purani functionality sahi chal rahi hai ya nahi.

Example: Password reset fix kiya → ab login bhi dobara test karna padega.
Easy Line: "New changes ke baad old features check karna = Regression Testing"

52. Boundary Value Analysis & Equivalence Partitioning

🔹 Boundary Value Analysis (BVA)
English: BVA means testing the boundary (edge) values of input range.
Example: Age limit = 18 to 60. Test: 17, 18, 19, 59, 60, 61.
Easy Line: "Testing edge values = BVA"

Hinglish: BVA me hum input ke starting aur ending values pe testing karte hain.
Example: Age = 18–60 → test 17, 18, 60, 61.
Easy Line: "Boundary values pe testing = BVA"

---

🔹 Equivalence Partitioning (EP)
English: EP means dividing data into groups (valid & invalid) and testing one value from each group.
Example: Valid: 18–60 → test 25; Invalid: <18 → test 15; Invalid: >60 → test 65.
Easy Line: "Divide data into groups and test one value = EP"

Hinglish: EP me data ko groups me divide karte hain (valid/invalid) aur har group se ek value test karte hain.
Easy Line: "Data ko group me divide karke test karna = EP"

Visualizing ECP & BVA (Input Range: 18 to 60)

53. Smoke Testing vs Sanity Testing

🔹 Smoke Testing
English: Smoke testing checks whether the basic functionality of the application is working.
Example: Login page opens, homepage loads.

Hinglish: Smoke testing me check karte hain ki application basic level pe chal rahi hai ya nahi.

---

🔹 Sanity Testing
English: Sanity testing checks a specific functionality after a small change or bug fix.
Example: Only test login after login bug fix.

Hinglish: Sanity testing me sirf wahi part test karte hain jahan change hua hai.

✅ Easy Difference:
English: Smoke = "Is system working?"; Sanity = "Is the fix working?"
Hinglish: Smoke = "System chal raha hai?"; Sanity = "Jo fix hua wo sahi hai?"

54. Bug found after Release - What will you do?

English:
1. Check severity and impact, 2. Log the bug, 3. Inform team/stakeholders, 4. Provide workaround, 5. Fix the bug, 6. Re-test (regression testing).

Example: Payment failure → High priority → Fix immediately.

Hinglish:
1. Impact check karo, 2. Bug log karo, 3. Team ko batao, 4. Workaround do, 5. Fix karvao, 6. Dubara test karo.
Easy Line: "Find → Report → Fix → Test again"

55. What is Traceability Matrix (RTM)?

English: RTM is a document that maps requirements with test cases to ensure full coverage.
Example: Login requirement → TC1, TC2.
Easy Line: "Requirement covered or not → RTM shows it"

Hinglish: RTM ek document hota hai jo requirement ko test cases se connect karta hai.
Easy Line: "Koi requirement miss na ho → RTM help karta hai"

56. Severity vs Priority

English:
* Severity: How serious the bug is
* Priority: How quickly it should be fixed

Examples:
* System crash → High severity, High priority
* Typo mistake → Low severity, High priority
Easy Line: "Severity = Impact, Priority = Urgency"

Hinglish:
* Severity: Bug kitna serious hai
* Priority: Bug ko kitni jaldi fix karna hai
Easy Line: "Severity = Impact, Priority = Jaldi fix karna"

Severity vs Priority Matrix (with QA Examples)

High Severity / High Priority

Defect: Crash on payment checkout page.

Why: The main user flow is completely blocked (High Severity) and it impacts revenue directly (High Priority).

Low Severity / High Priority

Defect: Company Logo is misspelled on the homepage.

Why: Doesn't block functionality (Low Severity), but severely hurts branding & reputation (High Priority).

High Severity / Low Priority

Defect: Application crashes when running on very old IE 9.

Why: Major code crash (High Severity), but active user base on IE 9 is under 0.1% (Low Priority).

Low Severity / Low Priority

Defect: A minor text spacing typo in privacy policy footer.

Why: Purely cosmetic issue (Low Severity) in a non-critical, rarely accessed footer (Low Priority).

57. Test Plan vs Test Strategy

🔹 Test Strategy
English: High-level document that defines how testing will be done.
Example: We will use manual + automation testing.

Hinglish: Test strategy high-level approach hota hai (kaise testing karenge).

---

🔹 Test Plan
English: Detailed document that includes scope, timeline, resources, and team.
Example: 5 testers, 10 days, tools used.

Hinglish: Test plan detailed document hota hai (kaun karega, kab karega, kaise karega).

✅ Easy Difference:
English: Strategy = "What & How"; Plan = "Who, When, How much"
Hinglish: Strategy = "Kaise karenge"; Plan = "Kaun karega, kab karega"

📌 Advanced Strategies & Scenarios (Advanced Level)

58. What is the V-Model in Testing?

The V-Model (Verification & Validation)

English: Associates every development phase with a corresponding test phase.
Hinglish: Har development step ke saath ek testing step parallel chalta hai.
Example: Requirement analysis matches Acceptance testing.

59. Explain Risk-Based Testing.

English: Focusing core efforts on features most likely to fail or cause damage.
Hinglish: Jahan zyada risk hai, wahan pehle aur zyada testing karna.
Example: Testing Payment gateway before About Us page.

60. What is Mutation Testing?

English: Changes (mutants) are made to source code to verify test case quality.
Hinglish: Code mein jaan-bujh kar galti karna dekhne ke liye ki tests use pakadte hain ya nahi.
Example: Changing a '+' to '-' in code to see if tests fail.

61. What is Shift-Left Testing?

English: Integrating testing into the early stages of the software development lifecycle.
Hinglish: Testing ko development process mein jaldi shuru karna, taaki bugs pehle mil jaayen.
Example: Developers writing unit tests before integration.

62. What is Test Pyramid?

English: Suggests having more low-level tests (unit) and fewer high-level tests (UI).
Hinglish: Testing ko alag-alag levels mein baantna, jaise zyada unit tests aur kam UI tests.
Example: Many unit tests, fewer integration tests, very few UI tests.

63. What is a 'Showstopper' bug?

English: A defect that is so severe it halts the entire project or prevents a release.
Hinglish: Ek aisa bug jo software ko release hone se rok de, bahut serious.
Example: The entire application crashes on startup in production environment.

64. Define 'State Transition Testing'.

English: Useful for systems with complex flows where outputs depend on the current state.
Hinglish: Jab system ek status se doosre par jaye (jaise Order status), use check karna.
Example: Ordered -> Packed -> Shipped -> Delivered.

65. What is 'Penetration' testing?

English: Ethical hacking to check for vulnerabilities and security gaps.
Hinglish: System ki suraksha check karne ke liye 'hacking' style testing.
Example: Trying to bypass login via SQL injection.

66. What is 'Cyclomatic Complexity'?

English: Quantitative measure of code complexity indicating the number of linearly independent paths.
Hinglish: Code kitna uljha hua hai, uska ek mathematical score.
Example: Score > 10 means code is complex and risky.

67. Difference between 'Load' and 'Stress' testing?

English: Load checks performance under expected peak; Stress checks stability beyond limits.
Hinglish: Load: 100 log; Stress: 10,000 log jab tak site fat na jaye.
Example: Normal sale vs Black Friday peak.

68. What is 'Interoperability' testing?

English: Focuses on the ability of different systems or components to exchange and use information.
Hinglish: Alag-alag systems ke beech data transfer aur communication check karna.
Example: Checking if app works properly with a PayPal API.

69. What are the key elements of a Bug Report?

English: ID, Title, Description, Steps to Reproduce, Expected vs Actual Results, Severity, Priority, Environment, and Attachments.
Hinglish: Bug report mein: ID, Title, Steps, Expected/Actual results, Severity aur screenshots zaroori hote hain.

70. What is 'Defect Leakage'?

English: When a bug is missed by testers and found by the customer/end-user after release.
Hinglish: Jab tester se bug miss ho jaye aur wo sidha client ke haath lag jaye.

71. Define 'Exploratory' testing simplified.

English: Simultaneous learning and execution to find bugs that scripted tests miss.
Hinglish: Bina kisi script ke app ko explore karke galti dhoondhna.

72. What do you do if a bug is not reproducible?

English: Check different browsers/OS, verify steps, consult developers, and monitor logs. Mark as 'Cannot Reproduce' if consistent.
Hinglish: Browser badal kar check karein, logs dekhein, developer se baat karein. Agar phir bhi na mile toh 'CNR' mark karein.

73. What is 'Sanity' vs 'Regression'?

English: Sanity checks limited fixes/new features; Regression checks everything old is still safe.
Hinglish: Sanity matlab naye badlav ki basic check. Regression matlab purana sab sahi hai ya nahi.

74. What is 'Localization' vs 'Globalization'?

English: Globalization makes the app ready for world; Localization adapts it to a specific city/culture.
Hinglish: Globalization app ko world-ready banata hai; Localization kisi khas jagah (like India) ke hisab se dhalta hai.

75. Define 'Smoke' testing goal.

English: To decide whether the build is stable enough for further detailed testing.
Hinglish: Ye decide karna ki build aage test karne layak hai ya nahi.

76. What is a 'Test Suite'?

English: A collection of multiple test cases grouped based on a feature or objective.
Hinglish: Bahut saare test cases ka ek group (bundle).

77. What is 'Static Testing' vs 'Dynamic Testing'?

English: Static doesn't execute code (Reviews); Dynamic executes code (Execution).
Hinglish: Static: Code review/Docs; Dynamic: App run karke check karna.

78. What is 'Verification' vs 'Validation' in one line?

English: Verification is 'Process' check; Validation is 'Product' check.
Hinglish: Verification: Kaam sahi ho raha hai? Validation: Product sahi bana hai?

79. Define 'Agile Scrum' in testing context.

English: Continuous testing and feedback throughout short development cycles (Sprints).
Hinglish: Chhote cycles (Sprints) mein kaam karna aur saath-saath test karna.

80. What is 'User Story'?

English: An informal, natural language explanation of a feature from the perspective of an end-user.
Hinglish: User ki nazar se ek feature ka chhota sa description.

81. What is 'Acceptance' testing types?

English: Alpha (Internal), Beta (External), and UAT (Business).
Hinglish: Alpha (team), Beta (real users), UAT (client).

82. What is 'Exploratory' testing duration typically?

English: Usually structured into 'sessions' of 30-90 minutes.
Hinglish: Ise 30-90 minutes ke sessions mein baant kar kiya jata hai.

83. What is 'Hotfix' vs 'Release'?

English: Hotfix is an emergency patch; Release is a planned deployment.
Hinglish: Hotfix emergency theek-kaam hai; Release ek planned launch.

84. Define 'Test Coverage' (Metric).

English: A metric measuring how much of the code/requirements are being exercised by tests.
Hinglish: Kitna software test kiya gaya, uska andaza lagana.

85. What is 'White Box' testing level?

English: Primarily Unit and Integration testing done by developers.
Hinglish: Jab coder khud code ki logic check kare.

86. Why is testing never 100%?

English: Due to infinite input combinations, time constraints, and environment variations.
Hinglish: Ananth combinations aur kam time ki wajah se 100% testing namumkin hai.