Fundamentals of Software Testing Flashcards

Which of the following statements best describes the difference between testing and debugging?

Answer: Testing aims to cause failures and find defects, while debugging is the process of finding, analyzing, and removing the causes of failures.

According to the ISTQB, testing and debugging are distinct activities. Testing is the process of finding defects, which may cause failures. Debugging is the development activity that involves finding the root cause of a failure (the defect), analyzing it, and fixing it.

A testing team has been using the same set of test cases for a system for multiple release cycles. Over time, they find that these tests are no longer discovering new defects. Which testing principle does this scenario illustrate?

Answer: Pesticide paradox.

The pesticide paradox principle states that if the same tests are repeated over and over again, eventually the same set of test cases will no longer find any new defects. To overcome this, test cases need to be regularly reviewed and revised, and new and different tests need to be written to exercise different parts of the software or system.

During which activity of the Fundamental Test Process are the overall testing objectives and test approach defined?

Answer: Test Planning and Control

Test Planning and Control is the initial activity in the Fundamental Test Process. During this phase, the scope, objectives, risks, and overall approach to testing are determined. This includes defining the test strategy, scheduling activities, and specifying the resources needed.

A tester is reviewing the system requirements specification to check for ambiguities and contradictions before any code is written. What type of testing is being performed?

Answer: Static Testing

Static testing involves the examination of work products, such as requirements, design documents, or code, without executing the software itself. Reviews, walkthroughs, and static analysis are common static testing techniques used to find defects early in the lifecycle.

Which of the following is a primary objective of Acceptance Testing?

Answer: To establish confidence that the system meets the needs of the users and stakeholders.

Acceptance Testing is a test level that focuses on determining whether the software is fit for purpose and meets the business and user requirements. Its main objective is to build confidence that the system is ready for deployment and use by end-users.

A project manager states, "We have run all our tests and have found no errors, therefore the software is ready for release." This statement is an example of which testing principle?

Answer: Absence-of-errors fallacy.

The 'Absence-of-errors fallacy' principle warns that finding and fixing many defects does not guarantee a successful system. The system could still be unusable if it doesn't meet user needs and expectations, even if it is 99% bug-free. Testing must also validate that the right system was built.