Q64. What is the Fish Model in Testing?
Answer:
The Fish Model (also known as the Fishbone Model) explains the correlation between development phases and corresponding test phases.
It has the structure of a fish:
- On the left side, development stages such as Requirements, Analysis, Design, Coding are detailed.
- On the right side, testing phases such as Reviews, Prototype Reviews, White Box Testing, System Testing align with each development phase. This model emphasizes early testing, also known as the shift-left approach.
Q65. What is Conformance Testing?
Answer:
Conformance Testing is used to verify whether a system complies with a set of defined standards or specifications.
Example scenarios:
- Verifying whether a browser conforms to W3C standards.
- Checking if APIs adhere to RESTful specifications. It ensures interoperability, reliability, and adherence to industry benchmarks.
Q66. What is Context-Driven Testing?
Answer:
Context-Driven Testing is a flexible testing approach where the testing strategy is influenced by:
- Project constraints (time, budget).
- Business objectives.
- Stakeholder priorities.
- Tester skill set.
This model opposes a “one-size-fits-all” strategy and promotes exploratory and adaptive testing based on the current project situation. It is part of the Agile Testing school.
Q67. What is End-to-End (E2E) Testing?
Answer:
E2E Testing involves validating the flow of an application from start to finish, covering all integrated components and subsystems. Goals:
- Mimic real-world user scenarios.
- Test communication with external systems (databases, APIs, hardware). Example: In an e-commerce app, an E2E test would simulate a user login → product search → add to cart → checkout → order confirmation.
Q68. When Should Testing End in a Project?
Answer:
Testing doesn’t truly “end” but is suspended based on multiple conditions:
- All high-priority test cases executed and passed.
- Defect rate drops below threshold.
- Project deadline or budget exhausted.
- Acceptance criteria met.
- Client approval received. However, residual risks may still exist, which is why post-release support and monitoring are essential.
Q69. What is Parallel or Audit Testing?
Answer:
In Parallel Testing, outputs from a new system are compared with those of an existing system to ensure accuracy and consistency.
For example, a new banking application will run parallel with the current one, and outputs such as transaction logs, interest calculations, and balances are verified. This approach is useful during data migration and system upgrades.
Q70. Roles of Glass-box and Black-box Testing Tools?
Answer:
- Black-box Tools (e.g., Selenium, QTP): Focus on UI and functionality. Do not require internal code knowledge.
- White-box/Glass-box Tools (e.g., JUnit, NUnit, Clover): Used for testing code logic, branches, paths, loops, and conditions. Use cases:
- Black-box: Validate login functionality.
- White-box: Ensure 100% path coverage inside the login logic.
Q71. How Do You Handle Change Control in a Small Team?
Answer:
Even in small teams, change control is critical to prevent scope creep and ensure traceability.
Best practices include:
- Using version control tools (Git, SVN).
- Maintaining a Change Request Document (CRD).
- Impact analysis.
- Test case re-evaluation and regression testing. Proper change control ensures that test artifacts remain consistent with the evolving application.
Q72. What is Gap Analysis in Testing?
Answer:
Gap Analysis in testing identifies the difference between the current state of the system and the desired requirements.
Tools like the Traceability Matrix are used to:
- Map each requirement to test cases.
- Identify missing test coverage.
- Ensure no requirement is overlooked. This is essential for requirement completeness and compliance audits.
Q73. How Do You Know Code Meets Specifications?
Answer:
Use a Requirement Traceability Matrix (RTM) to map:
- Each requirement ➝ Corresponding test case ➝ Test result. Once all mapped test cases pass successfully, we conclude that the system meets its specifications.
Q74. At What Stage Should Testing Begin in SDLC?
Answer:
Testing should begin from the requirement gathering phase (Shift-Left Testing).
Activities include:
- Reviewing BRS/SRS documents.
- Raising ambiguities early.
- Participating in requirement and design reviews. Early testing helps reduce defect injection rate and cost of bug fixing in later phases.
Q75. What Are the Characteristics of a Good Requirement?
Answer:
A good requirement should be:
- Clear – No ambiguity.
- Complete – Includes all necessary details.
- Consistent – No contradictions.
- Testable – Can be verified.
- Feasible – Realistic and implementable.
- Traceable – Can be tracked across the lifecycle.
Q76. How Do You Scope, Organize, and Execute a Test Project?
Answer:
- Scoping: Identify features/modules to test using SRS/FRS.
- Organizing: Assign tasks, plan timelines, and allocate resources.
- Execution: Prepare test cases, set up environments, execute tests, log defects, and generate reports. Tools like JIRA, TestRail, and Trello help in project tracking.
Q77. How to Ensure 100% Testing Coverage?
Answer:
True 100% testing is impractical, but high coverage can be ensured by:
- RTM to cover all requirements.
- Code coverage tools to measure branch, path, and statement coverage.
- Risk-based testing to prioritize critical areas.
- Ensuring positive and negative test cases are executed. Indicators of near-complete testing:
- All P0/P1 bugs are closed.
- Regression cycles are stable.
- Acceptance testing is passed.
Q78. How to Test a Web Application Effectively?
Answer:
To test a web application:
- Focus on both client-side (UI) and server-side (API, DB).
- Types of testing to apply:
- Functionality Testing
- Usability Testing
- Security Testing
- Performance Testing
- Compatibility Testing (Browser/OS)
- Accessibility Testing Test strategies depend on risk, complexity, and user base. Tools like Selenium, JMeter, Burp Suite, and BrowserStack are commonly used.
- Functionality Testing
Q79. What Are Your Core Strengths as a Tester?
Answer:
My strengths include:
- Strong analytical and problem-solving skills.
- Attention to detail and persistence.
- Excellent communication for bug reporting and team collaboration.
- Quick learning ability for new tools or domains.
- Adaptability to different methodologies (Agile, Waterfall).
Q80. When Should Testing Begin and End in a Project?
Answer:
- Start: During the requirement analysis phase to ensure testability.
- End: When:
- All major functionalities are verified.
- Critical defects are resolved.
- Acceptance criteria are met.
- Stakeholders sign off the release. However, testing never truly ends due to post-production activities like maintenance and monitoring.
- All major functionalities are verified.
