Q41. What is Equivalence Partitioning and how is it useful in test case design?
Ans:
Equivalence Partitioning is a black-box testing technique used to reduce the total number of test cases while still covering maximum functionality. It divides input data into valid and invalid partitions. Test cases are then designed to cover each partition at least once.
Steps:
- Identify valid and invalid equivalence classes.
- Design test cases for each class.
Example: If valid quantity is -9999 to 9999, test cases should include:
- A valid case: (e.g. QTY = 0)
- An invalid case below the range: (QTY < -9999)
- An invalid case above the range: (QTY > 9999)
Q42. What are the two main types of metrics in software testing?
Ans:
- Process Metrics: Focus on process performance (e.g., defect density, test execution rate).
- Product Metrics: Measure product attributes like code complexity, design quality, and size.
Q43. What is the expected outcome of software testing?
Ans:
The goal is to deliver a stable application that performs as expected under defined conditions.
Q44. Why is White Box Testing needed when Black Box Testing exists?
Ans:
White Box Testing allows testers to verify internal logic such as loops, conditions, and code structure. This complements Black Box Testing, which focuses on external functionality, ensuring more robust testing coverage.
Q45. What is a Baseline Document in testing? Provide examples.
Ans:
A Baseline Document serves as a reference point before actual testing begins. Examples:
- Business Requirement Document (BRD)
- Functional Specification Document (FSD)
Q46. Name a few testing types you have worked with or learned about.
Ans:
- Smoke Testing
- Sanity Testing
- Ad-hoc Testing
- Performance Testing
- Recovery Testing
- Security Testing
- Web Testing
- Customer Experience Testing (CET)
Q47. What is the Heuristic Checklist Approach in Unit Testing?
Ans:
This approach uses experience-based techniques and predefined checklists to guide unit testing. It helps in identifying potential defects by using best practices and known problem areas.
Q48. What is meant by Data Guidelines in testing?
Ans:
Data Guidelines define the necessary data parameters required to design and execute test cases. They help testers prepare appropriate test data for various scenarios based on the specifications.
Q49. Why is a Test Bed important in testing?
Ans:
A Test Bed provides the required test data and environment to compare actual results against expected results. It ensures consistent and accurate test execution.
Q50. Why do we prepare Test Conditions, Test Cases, and Test Scripts before testing begins?
Ans:
These artifacts are essential for structured testing. They define “what” to test (conditions), “how” to test (cases), and “how to execute” (scripts), making the process efficient and traceable.
Q51. Is preparing test documentation a waste of time?
Ans:
No. Test documentation like test cases and scripts is critical for maintaining quality, repeatability, and accountability in the testing process.
Q52. How do you approach Web Application Testing?
Ans:
Focus areas include:
- Performance and load behavior
- Data transfer between client-server
- Security (authentication, encryption)
- Functionality across different browsers and devices
Q53. Which documents are needed for Functional Testing?
Ans:
- Functional Specification Document (FSD)
- Business Requirement Document (BRD)
- Gap Analysis Document
- User Manuals
Q54. Can System Testing be done at any stage?
Ans:
No. System Testing is performed only after all modules are integrated and functioning properly. It typically follows integration testing and precedes UAT (User Acceptance Testing).
Q55. What is Mutation Testing and when is it performed?
Ans:
Mutation Testing introduces small changes (mutants) to code to assess whether the existing test cases can detect them. It validates the effectiveness of unit test cases.
Q56. Why is it impossible to test a program completely?
Ans:
Complete testing is unachievable due to:
- Infinite input combinations
- Numerous execution paths
- Subjective requirements and human error in interpreting specs
Q57. What are the different types of test case reviews?
Ans:
- Informal Review
- Peer Review
- Management Review
- Technical Review
- Formal Review (Inspections & Audits)
Objective: Identify defects early and improve process quality.
Q58. What is Pilot Testing?
Ans:
Pilot Testing simulates the production environment with a small group of real users before full-scale deployment. It helps identify high-priority issues and ensures system readiness.
Q59. What is the difference between BRS and SRS?
Ans:
- BRS (Business Requirement Specification): High-level requirements from the client’s perspective.
- SRS (Software Requirement Specification): Detailed, technical translation of BRS for developers and testers.
Q60. What is the difference between Smoke Testing and Sanity Testing?
Ans:
- Smoke Testing: Basic checks to ensure build stability for further testing.
Sanity Testing: Focused checks to verify specific functionality after changes.
Smoke = Build level; Sanity = Release level
👉The Next 20 Questions-II: MANUAL TESTING
