61. What is Debugging?
Answer:
Debugging is the process of identifying, analyzing, and removing bugs or defects in software code. It is performed by developers to resolve issues that cause the program to behave unexpectedly.
62. What is Determination in Software Testing Context?
Answer:
In testing, determination can refer to the act of concluding a specific testing outcome based on evaluation. More generally, it reflects a tester’s strong commitment to achieving quality goals and ensuring software reliability.
63. Difference Between Debugging and Testing
Answer:
- Testing: Performed by testers to identify defects in the software.
- Debugging: Carried out by developers to analyze and fix the defects found during testing.
64. What is the Fish Model in Testing?
Answer:
The Fish Model maps each software development stage to a corresponding testing phase:
- Requirements → Reviews
- Analysis → SRS Reviews
- Design → HLD/LLD Reviews
- Coding → White-box Testing
- Testing → Black-box Testing
- Release → Maintenance
65. What is Conformance Testing?
Answer:
Conformance testing verifies whether a system meets the specified standards or regulations. It’s commonly used when validating software against industry protocols or formal documentation.
66. What is Context-Driven Testing?
Answer:
A form of Agile testing where test strategies are tailored based on the project’s specific needs and context. It emphasizes continuous learning, flexibility, and real-time decision-making.
67. What is End-to-End Testing?
Answer:
End-to-end testing involves validating an entire application flow, including database interactions, network communications, and integration with other systems—simulating real-world usage.
68. When Should Testing Be Stopped?
Answer:
Testing can be concluded when:
- All major test cases are executed.
- Deadlines or budgets are reached.
- Bug rate drops below acceptable limits.
- Risk is considered minimal.
69. What is Parallel/Audit Testing?
Answer:
This testing technique compares outputs from a new system with an existing one to ensure accuracy. It’s commonly used during system migrations or upgrades.
70. Roles of Black-box and White-box Testing Tools
Answer:
- Black-box: Validates functionality without internal code knowledge.
- White-box: Validates internal logic, covering code paths, decisions, and loops.
71. What is Your Experience with Change Control in Small Teams?
Answer:
Change control ensures consistency between product development and documentation, even in small teams. It helps in tracking changes and maintaining alignment with project goals.
72. What is Gap Analysis?
Answer:
Gap analysis identifies missing elements by comparing the Software Requirements Specification (SRS) with test cases using tools like a traceability matrix.
73. How Do You Know If Code Meets Requirements?
Answer:
By using a traceability matrix to ensure each requirement has been tested through corresponding test cases. Full test pass indicates compliance.
74. When Should Testing Start in the Software Life Cycle?
Answer:
Testing should begin during the requirements phase to ensure that all specifications align with client expectations, followed by design, development, and execution phases.
75. Characteristics of a Good Requirement
Answer:
A good requirement is:
- Clear
- Complete
- Testable
- Attainable
- Cohesive
- Reasonably Detailed
76. How Do You Scope, Organize, and Execute a Test Project?
Answer:
- Scope: Defined from BRS, SRS, or FRS.
- Organize: Allocate resources, define responsibilities, identify risks.
- Execute: Follow the planned test strategy with clear priorities.
77. How to Ensure 100% Test Coverage?
Answer:
Absolute 100% coverage is impractical, but the goal is to:
- Execute all planned test cases.
- Close all high-priority bugs.
- Cover all functionalities and risk areas.
- Ensure requirements traceability.
78. How to Test a Web Application?
Answer:
Testing includes:
- Functionality Testing
- GUI Testing
- Security & Performance Testing
- Compatibility Testing
- Client-server Architecture Testing
Prioritize areas based on risk, requirements, budget, and time.
79. What Are Your Strengths as a Tester?
Answer:
- Self-motivated
- Detail-oriented
- Team player
- Quick learner
- Strong communication and analytical skills
80. When Should You Begin Testing in a Project?
Answer:
Testing starts right after requirement gathering. Early testing includes:
- Requirement validation
- Design reviews
- Unit testing
- Integration and functional testing post-build
