2. How does quality control differ from quality assurance?

3. Why is Software Testing Required?

4. What are the two main categories of software testing?

5. What is quality control? Is it similar to Quality Assurance?

6. What different types of manual testing are there?

7. Explain the difference between alpha testing and beta testing.

8.Why is it that the boundary value analysis provides good test cases?

9. What is a testbed in manual testing?

10. Explain the procedure for manual testing?

11. What is a test scenario?

12. What is GUI testing?

13. When should testing end?

14. What are the different types of Software testing?

15. What is Acceptance testing?

16. Differentiate between bug leakage and bug release

17. What is a test script?

18. What’s the difference between verification and validation in testing?

19. What’s the difference between a bug and a defect?

20.What are the advantages of manual testing?

21.What are the drawbacks of manual testing?

22. What’s the role of documentation in Manual Testing?

23. What is the difference between manual testing and automation testing?

24. When should you opt for manual testing over automation testing?

25. What are the phases involved in Software Testing Life Cycle?

26. What is the difference between a bug, a defect and an error?

27. What makes a good test engineer?

28.What is regression testing? When to apply it?

29. What is the difference between system testing and integration testing?

30. Explain the defect life cycle.

31. What is the test harness?

32. What is test closure?

33. What is the difference between Positive and Negative Testing?

34. What is your approach towards a severely buggy program? How would you handle it?

35. What is the pesticide paradox? How to overcome it?

36. What is Defect Cascading in Software Testing?

37. What is the term ‘quality’ mean when testing?

38. What is black box testing, and what are the various techniques?

39. What is white box testing, and what are the various techniques?

40. What are the Experience-based testing techniques?

41.What is a top-down and bottom-up approach in testing?

42. What is the difference between smoke testing and sanity testing?

43. What is the difference between static testing and dynamic testing?

44. How will you determine when to stop testing?

44. What if the software is so buggy it can’t really be tested at all? 

45. How you test a product if the requirements are yet to freeze?

46. What if an organization is growing so fast that fixed testing processes are impossible? What to do in such situations?

47. What is a cause-effect graph?

48. What are the cases when you’ll consider to choose automated testing over manual testing?

49. What is ‘configuration management’?

50. Is it true that we can do system testing at any stage?

51. What are some best practices that you should follow when writing test cases?

Manual Testing Interview Questions And Answers

1. What is Software Testing?
   Ans. Software Testing is the process of evaluating a software application to identify any discrepancies between the expected and actual results. The goal is to ensure that the software meets specified requirements, is free of defects, and functions as intended.
2. How does quality control differ from quality assurance?

Ans.

• Quality Control (QC): Focuses on identifying and fixing defects in the product. It is a reactive process that occurs after the product is developed.
• Quality Assurance (QA): Involves activities that ensure the processes, methods, and standards used for developing the product are appropriate. QA is a proactive process that aims to prevent defects.

3.Why is Software Testing Required?

Ans.

• Software Testing is crucial for various reasons:
  • Identifying defects and issues early in the development process.
  • Ensuring the software meets user requirements.
  • Enhancing the reliability and quality of the software.
  • Reducing the risk of software failure in the production environment.

4. What are the two main categories of software testing?

Ans.

• Manual Testing: Testers manually execute test cases without using any automation tools.
• Automated Testing: Testers use automation tools to execute test scripts and compare actual outcomes with expected outcomes.

5.What is quality control? Is it similar to Quality Assurance?

Ans.

• Quality Control (QC): The process of ensuring that the product meets the specified requirements and is free of defects. It is a reactive process that involves testing and fixing defects.
• Quality Assurance (QA): The process of ensuring that the processes, methods, and standards used for developing the product are appropriate. QA is a proactive process aimed at preventing defects.

6. What different types of manual testing are there?

Ans.

• Unit Testing: Testing individual components or modules.
• Integration Testing: Testing the combination of multiple components.
• System Testing: Testing the entire system as a whole.
• Acceptance Testing: Ensuring the software meets user requirements.

7.Explain the difference between alpha testing and beta testing.

Ans.

• Alpha Testing: Conducted by the internal development team to identify issues before releasing the software to external users.
• Beta Testing: Conducted by a selected group of external users who test the software in a real-world environment before its official release.

8.Why is it that the boundary value analysis provides good test cases?

Ans.

Boundary value analysis is an effective testing technique because it targets potential errors at the boundaries of the input domain. Instead of focusing on the center of the range, this method emphasizes values at the edges and boundaries.

In the context of testing an input box accepting numbers from ’01 to 10′, boundary value analysis categorizes test cases into three classes:

1. Test cases at input boundaries: Includes values exactly at the boundaries, such as 1 and 10.
2. Values just below the extreme edges: Involves test data slightly below the minimum and maximum boundaries, like 0 and 9.
3. Test data just above the extreme edges: Covers values just above the minimum and maximum boundaries, such as 2 and 11.

In the given example, the boundary values to be tested are 0, 1, 2, 9, 10, and 11. This method ensures comprehensive testing by examining scenarios both within and just outside the specified boundaries, helping to uncover potential issues that might occur in real-world usage.

9.What is a testbed in manual testing?

Ans. A testbed in manual testing refers to the environment or infrastructure set up for conducting testing activities. It includes hardware, software, network configurations, and other necessary components essential for testing the software application. The testbed provides the necessary resources and conditions to execute test cases and evaluate the behavior of the software under various scenarios.

10.Explain the procedure for manual testing

Ans.

The procedure for manual testing typically involves the following steps:

a.Test Planning: Define the testing objectives, scope, and resources.

b.Test Case Design: Create test cases based on requirements and specifications.

c.Test Environment Setup: Set up the necessary hardware and software for testing.

d.Test Execution: Perform manual testing by executing test cases and recording results.

e.Defect Reporting: Document and report any defects or issues found during testing.

f.Regression Testing: Re-run test cases to ensure new changes haven’t introduced new defects.

g.Test Closure: Summarize test results, evaluate testing activities, and prepare test closure reports.

11.What is a test scenario?

Ans.A test scenario is a detailed description of a specific test case. It outlines the conditions, actions, and expected results of a particular testing activity. Test scenarios help in defining the scope of testing and guide testers in executing tests to ensure the software meets specified requirements.

12. What is GUI testing?

Ans.GUI (Graphical User Interface) testing is a type of software testing that focuses on verifying the functionality and appearance of the graphical elements of a user interface. It includes testing buttons, menus, icons, windows, and other visual components to ensure they respond correctly to user interactions and adhere to design specifications.

13.When should testing end?

Ans.

• The decision to end testing depends on various factors, including:
• Achievement of testing objectives.
• Sufficient test coverage.
• Meeting exit criteria.
• Time and budget constraints.
• Stability and reliability of the software.
• Approval from stakeholders.

14.What are the different types of Software testing?

Ans.

There are various types of software testing, including:

• Unit Testing
• Integration Testing
• System Testing
• Acceptance Testing
• Regression Testing
• Performance Testing
• Security Testing
• Usability Testing
• Compatibility Testing
• Exploratory Testing

15.What is Acceptance testing?

Ans. Acceptance testing is the final phase of testing where the software is evaluated to ensure it meets the specified business requirements. It is conducted to gain confidence that the system is ready for deployment. Types of acceptance testing include User Acceptance Testing (UAT), Business Acceptance Testing (BAT), and Operational Acceptance Testing (OAT). The primary goal is to validate that the software satisfies user expectations and is ready for production use.

Hridhya Manoj

Hello, I’m Hridhya Manoj. I’m passionate about technology and its ever-evolving landscape. With a deep love for writing and a curious mind, I enjoy translating complex concepts into understandable, engaging content. Let’s explore the world of tech together