Q41. Why should we use Equivalence Partitioning in Manual Testing?
Answer: Equivalence Partitioning is a black-box test design technique that helps in reducing the number of test cases while maintaining high test coverage. It works by dividing input data into valid and invalid partitions. This allows testers to identify representative test cases from each class, minimizing redundant tests. For instance, if a field accepts values from 1 to 100, testers can choose 3 classes: values within range (valid), below range (invalid), and above range (invalid). This drastically improves testing efficiency by finding more bugs with fewer test cases.
Q42. What are the two major types of software testing metrics?
Answer:
- Process Metrics: These evaluate the efficiency of the testing process itself. Examples include test execution time, defect removal efficiency, and defect density. Process metrics are useful for Six Sigma analysis and improving the overall development lifecycle.
- Product Metrics: These assess characteristics of the software product such as complexity, size, performance, or quality. Examples include code coverage, cyclomatic complexity, and number of defects found in modules.
Q43. What is the expected outcome of software testing?
Answer: The ideal outcome of software testing is a stable, reliable application that meets the expected business and functional requirements. Testing ensures that the software performs its intended tasks under defined conditions, and helps identify defects before production deployment.
Q44. Why perform White Box Testing when Black Box Testing is available?
Answer: White Box Testing complements Black Box Testing by validating the internal structure, logic, and code paths of the application. While black box focuses on user-level functionality, white box ensures the integrity of loops, conditions, and logic. This helps uncover issues like untested code branches, poor logic, and hidden bugs that black-box methods might miss.
Q45. What is a Baseline Document? Name two common baseline documents.
Answer: A Baseline Document is a finalized version of a project artifact that serves as a foundation for further development and testing. It provides traceability and consistency. Two commonly used baseline documents in manual testing are:
- Business Requirement Document (BRD)
- Functional Specification Document (FSD)
Q46. What types of testing have you experienced?
Answer: Examples of manual testing types include:
- Ad-Hoc Testing
- Sanity Testing
- Smoke Testing
- Security Testing
- Performance Testing
- Recovery Testing
- Web Application Testing
- Customer Experience Testing (CET)
Mentioning testing types relevant to the job role shows practical exposure.
Q47. What is the Heuristic Checklist Approach for Unit Testing?
Answer: This approach involves creating a checklist of testing heuristics or best practices that can guide developers/testers through the unit testing process. It helps in systematically uncovering defects by testing various aspects like boundary conditions, error handling, and logic coverage.
Q48. What is meant by Data Guideline in testing?
Answer: Data Guidelines define the format, type, and scope of test data required to validate test cases. It helps testers in preparing effective test scripts and scenarios by ensuring the right data sets are used, especially when conditions are derived from complex business logic.
Q49. Why do we need a Test Bed in manual testing?
Answer: A Test Bed is a controlled environment containing all necessary software, hardware, and network configurations required to perform testing. It ensures consistent results by providing a stable platform for executing test cases and comparing actual results against expected outcomes.
Focus Keywords: test bed setup in QA, manual testing environment, software QA tools.
Q50. Why is it essential to prepare Test Conditions, Test Cases, and Test Scripts before testing?
Answer: These are core test design documents. Test Conditions outline what to test, Test Cases specify how to test, and Test Scripts automate the execution process (in automation or tool-based testing). They help maintain clarity, ensure traceability, and maximize test coverage.
Q51. Is preparing test documents like Test Case and Script a waste of time?
Answer: Absolutely not. Test documentation ensures structured testing, reproducibility of defects, and validation of all requirements. Well-prepared test cases improve collaboration, maintain quality standards, and reduce chances of missing critical bugs.
Focus Keywords: importance of test cases, QA test planning, manual testing documentation.
Q52. How would you approach testing a Web Application?
Answer: Start by assessing performance, load handling, and scalability. Then, test data flow across front-end, middleware, and backend. Key testing areas include:
- Functional testing
- Security testing
- Browser compatibility
- Session management
- Data integrity
Q53. What documents are required for Functional Testing?
Answer: Primarily, the Functional Specification Document (FSD) is required. Additional documents like Business Requirement Specification (BRS), User Manuals, and Gap Analysis Reports help validate expected behavior against actual system output.
Q54. Can System Testing be performed at any stage?
Answer: No. System Testing is a high-level testing performed only after all modules are integrated and unit testing is complete. It validates end-to-end application behavior and should precede UAT (User Acceptance Testing).
Q55. What is Mutation Testing and when is it used?
Answer: Mutation Testing is a unit testing technique where small code changes (mutants) are introduced to evaluate whether existing test cases detect the errors. It assesses the quality and robustness of test cases and is often used in advanced fault-based testing scenarios.
Q56. Why is complete testing of a program impossible?
Answer: Because of the vast number of possible input combinations, outputs, paths, and user interactions, it is practically infeasible to test every possible scenario. Also, subjective requirements and dynamic behavior make 100% testing unattainable.
Q57. How do you review a Test Case? What are the types of reviews?
Answer: Test case reviews ensure quality and correctness. Types include:
- Informal Review
- Peer Review
- Technical Review
- Management Review
- Walkthroughs
- Formal Inspections
Goals are to identify defects, improve documentation quality, and align with test goals.
Q58. What is Pilot Testing?
Answer: Pilot Testing involves limited release of the software to a subset of users before final deployment. It simulates the production environment and checks real-time functionality, often helping to catch critical issues early. It occurs between UAT and Production.
Q59. What is the difference between SRS and BRS?
Answer:
- BRS (Business Requirement Specification): Defines what the client expects the system to do.
- SRS (Software Requirement Specification): Translates BRS into technical software requirements — how the system will achieve those goals.
Q60. What is the difference between Smoke Testing and Sanity Testing?
Answer:
- Smoke Testing: Performed on new builds to check for testability and major issues. Also called “build verification testing.”
- Sanity Testing: A quick test to ensure core functionalities work after minor changes or bug fixes. Acts as a subset of regression testing.
The Next 20 Questions-II: MANUAL TESTING
