type of testing

Functional Testing ▶
API Testing Interview Smoke Testing Sanity Testing System Testing Unit Testing Integration Testing Regression Testing User Acceptance Testing (UAT) Interface Testing End-to-End Testing Compatibility Testing
Non-Functional Testing ▶
Performance Testing Load Testing Stress Testing Scalability Testing Usability Testing Security Testing Recovery Testing Maintainability Testing Reliability Testing Compliance Testing Accessibility Testing
Chapter 1: Introduction
Topic 1.1: What is Java? Topic 1.2 Comments & Identifiers
Chapter 2: Variables & Data Types Chapter 3: Control Statements Chapter 4: OOP Concepts Chapter 5: Inheritance
SQL

Search

Total Views

Total Views:

Manual Testing Interview Questions and Answers part 02

← back

✅ Manual Testing Basics

  1. What is manual testing?
    Answer: Manually checking the software for bugs without using automation tools.
    Example: Opening a login page and entering different usernames to test it.

  2. Why do we do testing?
    Answer: To find bugs and ensure the software works as expected.
    Example: Checking if the "Add to Cart" button on an e-commerce site works.

  3. What is a bug?
    Answer: An error or issue in the software that causes incorrect results.
    Example: Clicking a button, but nothing happens.

  4. What is a test case?
    Answer: A set of steps to check if a feature works correctly.
    Example: Step 1: Open login page → Step 2: Enter valid credentials → Step 3: Click login.

  5. What is test data?
    Answer: The data used for testing.
    Example: Username: user123, Password: pass123.

  6. What is a test plan?
    Answer: A document that explains what to test, how to test, and who will test.
    Example: A test plan for a banking app includes testing login, balance check, and transactions.

  7. What is a test scenario?
    Answer: A high-level idea of what to test.
    Example: Test the search feature on an e-commerce website.

  8. What is a test script?
    Answer: A set of instructions used in automation testing. (Not used in manual testing but good to know.)

  9. What is QA (Quality Assurance)?
    Answer: A process to ensure quality in the software development.
    Example: Reviewing requirements before development starts.

  10. What is QC (Quality Control)?
    Answer: Finding bugs in the final product.
    Example: Testing the website after it’s developed.

✅ Types of Testing

  1. What is functional testing?
    Answer: Testing features like login, signup, etc.
    Example: Checking if the login works properly.

  2. What is non-functional testing?
    Answer: Testing performance, security, usability, etc.
    Example: Checking if the website loads in 2 seconds.

  3. What is smoke testing?
    Answer: Basic testing to check if the main features work.
    Example: Checking if the app opens and login works.

  4. What is sanity testing?
    Answer: Quick testing after minor changes.
    Example: Developer fixes a login bug, you test just the login again.

  5. What is regression testing?
    Answer: Testing old features after new code is added.
    Example: After adding search feature, check if login still works.

  6. What is integration testing?
    Answer: Testing how modules work together.
    Example: Testing if login and dashboard work smoothly together.

  7. What is system testing?
    Answer: Testing the whole system as a user.
    Example: Testing the complete flow of an online shopping app.

  8. What is acceptance testing?
    Answer: Checking if the software meets business needs.
    Example: Client checks if the software works as they want.

  9. What is usability testing?
    Answer: Checking how easy the app is to use.
    Example: Seeing if users can easily find the logout button.

  10. What is compatibility testing?
    Answer: Testing on different devices and browsers.
    Example: Checking a site on Chrome, Firefox, and Edge.

✅ Bug Reporting and Tracking

  1. What is a defect life cycle?
    Answer: The journey of a bug from finding to closing.
    Example: New → Assigned → Fixed → Retest → Closed.

  2. What is severity?
    Answer: How serious the bug is for the system.
    Example: App crashes = High severity.

  3. What is priority?
    Answer: How soon the bug should be fixed.
    Example: Spelling mistake = Low severity but High priority if on home page.

  4. What is a bug report?
    Answer: A document that describes the bug in detail.
    Example: "Submit button not working on the Contact Us page."

  5. What is a defect?
    Answer: Another name for bug or error in software.

✅ Test Design Techniques

  1. What is boundary value analysis (BVA)?
    Answer: Testing at the edge of input values.
    Example: If age limit is 18–60, test 17, 18, 60, 61.

  2. What is equivalence partitioning?
    Answer: Dividing input into valid and invalid groups to reduce test cases.
    Example: Age: 1–100 → Group 1: 25 (valid), Group 2: -1 (invalid), Group 3: 150 (invalid).

  3. What is exploratory testing?
    Answer: Testing without any plan, just exploring the app.
    Example: Randomly clicking buttons and checking results.

  4. What is ad hoc testing?
    Answer: Informal testing done without test cases.
    Example: Trying out features as you wish.

  5. What is negative testing?
    Answer: Testing with invalid data.
    Example: Entering letters in a phone number field.

✅ Test Documentation

  1. What is a test strategy?
    Answer: A high-level document that explains how testing will be done.
    Example: It may say "We will do manual functional and regression testing."

  2. What is the difference between test case and test scenario?
    Answer:

  • Test Scenario: What to test

  • Test Case: How to test it
    Example:

  • Scenario: Test login

  • Case: Enter username, enter password, click login

  1. What should a test case include?
    Answer: Test case ID, steps, input, expected result, actual result, pass/fail.

  2. What is traceability matrix?
    Answer: A document that links test cases to requirements.
    Example: Req 1 → TC001, TC002

  3. Why is documentation important in testing?
    Answer: Helps track what is tested and ensures coverage.

✅ Real-Time Project Terms

  1. What is a test environment?
    Answer: A setup where testers test the app.
    Example: Browser, OS, database.

  2. What is test coverage?
    Answer: How much of the app is tested.
    Example: Out of 10 modules, 7 are tested → 70% coverage.

  3. What is test execution?
    Answer: Running the test cases.

  4. What is build?
    Answer: A version of the app given for testing.
    Example: Build 1.0, Build 1.1

  5. What is release?
    Answer: The final version delivered to the client or end-user.

✅ Agile and Testing

  1. What is Agile testing?
    Answer: Testing that happens in short cycles or sprints with development.
    Example: Test login in Sprint 1, payment in Sprint 2.

  2. What is a sprint?
    Answer: A 1–4 week cycle in Agile to deliver features.

  3. What is a daily stand-up?
    Answer: A short team meeting to discuss progress and blockers.

  4. What is user story?
    Answer: A short requirement from user’s view.
    Example: "As a user, I want to reset my password."

  5. What is sprint retrospective?
    Answer: A meeting to discuss what went well and what didn’t in a sprint.

✅ Common Interview Questions

  1. What will you do if you find a bug?
    Answer: Reproduce → Report with details → Attach screenshot or video.

  2. How do you handle a situation where the developer says it’s not a bug?
    Answer: Explain steps clearly, show requirements, discuss with the team.

  3. What if the requirements are unclear?
    Answer: Ask the business analyst or product owner for clarification.

  4. Do you write test cases before testing?
    Answer: Yes, mostly. But for exploratory/ad hoc, we may not.

  5. Have you done retesting?
    Answer: Yes, we retest bugs after developers fix them.

✅ Bug Tracking Tools

  1. What is JIRA?
    Answer: A tool used to manage bugs, tasks, and stories.

  2. What is Bugzilla?
    Answer: An open-source bug tracking tool.

  3. What is the use of a bug ID?
    Answer: Helps track and refer to bugs easily.

  4. What is status of a bug when first found?
    Answer: New.

  5. What is the final bug status after retest?
    Answer: Closed (if fixed), Reopened (if not fixed).

✅ Test Levels

  1. What is unit testing?
    Answer: Testing done by developers for small code units.

  2. What is integration testing?
    Answer: Testing how modules connect and work together.

  3. What is system testing?
    Answer: Testing the entire system end-to-end.

  4. What is acceptance testing?
    Answer: Done by client to accept or reject the software.

  5. Who performs unit testing?
    Answer: Developers.

✅ Examples and Scenarios

  1. Give an example of a high severity low priority bug.
    Answer: Crash in rarely used feature.

  2. Give an example of a low severity high priority bug.
    Answer: Spelling mistake in app name.

  3. What is cross-browser testing?
    Answer: Testing a site on Chrome, Firefox, Edge, etc.

  4. What is cross-platform testing?
    Answer: Testing an app on Android, iOS, and Windows.

  5. What is localization testing?
    Answer: Testing an app in different languages.
    Example: English, Hindi, German.

✅ Best Practices

  1. What is your daily routine as a tester?
    Answer: Read stories → Write test cases → Test → Raise bugs → Retest → Report.

  2. How do you prioritize test cases?
    Answer: Based on business impact and usage.

  3. Do you participate in requirement meetings?
    Answer: Yes, to understand what to test.

  4. Why is early testing important?
    Answer: Bugs found early are cheaper to fix.

  5. What is risk-based testing?
    Answer: Testing important features first based on risk.

✅ More Real-Time Questions

  1. What is a blocker bug?
    Answer: A bug that stops testing.
    Example: App doesn't open.

  2. How do you report bugs to a developer?
    Answer: In tools like JIRA, with steps, screenshots, expected vs actual result.

  3. What is a duplicate bug?
    Answer: A bug that is already reported.

  4. What is deferred bug?
    Answer: Bug that will be fixed later.

  5. What is closed bug?
    Answer: A bug that is fixed and verified

✅ Test Metrics and Reporting

  1. What are test metrics?
    Answer: Numbers that show the testing progress and quality.
    Example: Total test cases = 100, Passed = 90 → Pass rate = 90%

  2. What is defect density?
    Answer: Number of bugs per 1000 lines of code.
    Example: 5 bugs found in 1000 lines → defect density = 5.

  3. What is test effectiveness?
    Answer: It shows how good your testing is at finding bugs.
    Example: More bugs found by testers, higher effectiveness.

  4. What is test efficiency?
    Answer: How quickly and cost-effectively tests are done.

  5. What is the exit criteria in testing?
    Answer: Conditions to stop testing.
    Example: 100% test cases passed, no critical bugs open.

✅ More Testing Types

  1. What is alpha testing?
    Answer: Testing done by internal team before release.
    Example: Company employees test the app.

  2. What is beta testing?
    Answer: Testing done by real users before final launch.
    Example: Public gets early access to find issues.

  3. What is installation testing?
    Answer: Testing if software installs and uninstalls properly.
    Example: Install app on Android and see if it works.

  4. What is recovery testing?
    Answer: Checking if the app recovers after crash or failure.
    Example: App crash due to low battery, see if it opens correctly after restart.

  5. What is monkey testing?
    Answer: Random testing without any logic.
    Example: Randomly pressing buttons on the app.

✅ Advanced Questions Made Simple

  1. What is a hotfix?
    Answer: A quick fix released to fix a major bug in production.

  2. What is parallel testing?
    Answer: Testing same app on multiple environments.
    Example: Test on Chrome and Firefox at the same time.

  3. What is end-to-end testing?
    Answer: Testing complete user flow.
    Example: Register → Login → Search → Buy → Logout

  4. What is data-driven testing?
    Answer: Testing with different sets of data.
    Example: Checking login with 10 different usernames.

  5. What is UI testing?
    Answer: Testing how the interface looks and works.
    Example: Checking button alignment and color.

✅ Interview-Specific Situations

  1. What will you do if the developer doesn’t agree with your bug?
    Answer: Share steps, screenshots, or video proof. If still unclear, involve lead.

  2. How do you handle frequent requirement changes?
    Answer: Communicate with the team and update test cases accordingly.

  3. How do you test without requirements?
    Answer: Explore the app, ask stakeholders, and use domain knowledge.

  4. What is the difference between QA and QC?
    Answer:

  • QA = Preventing bugs

  • QC = Finding bugs after development

  1. What makes a good test case?
    Answer: Clear, simple, covers all steps, has expected result.

✅ Miscellaneous

  1. What is the role of a tester in Agile?
    Answer: Attend daily meetings, test stories, raise bugs, retest fixes.

  2. What is test data preparation?
    Answer: Creating data needed for testing.
    Example: Test user accounts, sample orders.

  3. What is A/B testing?
    Answer: Comparing two versions of a feature to see which performs better.

  4. What is black box testing?
    Answer: Testing without knowing the internal code.
    Example: Just test the login screen from the front end.

  5. What is white box testing?
    Answer: Testing with knowledge of code, done by developers.

← back

Subscribe to: Comments (Atom)

Comments

🌟🌟🌟🌟☆ Great platform with helpful onboarding! Some areas could be streamlined, but overall a very positive experience.