A bug or defect is:
A defect, also known as a bug, is a flaw in a component or system that can cause it to fail to perform its required function. Defects arise from errors made by people, such as mistakes in code or design. When a defect in the software is executed, it can cause the system to behave unexpectedly, leading to failures. The relationship between errors, defects, and failures is crucial to understanding the importance of early detection and correction in the software development lifecycle.
An input field takes the year of birth between 1900 and 2004. The boundary values for testing this field are:
Boundary value analysis focuses on the values at the edges of equivalence partitions. For an input range of 1900 to 2004, the boundary values are just inside and just outside the range:
Just inside: 1900, 2004
Just outside: 1899, 2005
Therefore, the boundary values are 1899, 1900, 2004, and 2005. Reference: ISTQB CTFL Syllabus V4.0, Section 4.2.1.
An iPhone application identifies and counts all purchases of a particular product from a shopping website. The application incorrectly counts purchase attempts by including both failed attempts, and also those where the purchase was terminated by the user before completion. Testing has identified that the problem was located in the 'purchase identification' module, where the first stage in the purchasing process was counted, rather than a successful confirmed purchase.
Which of the following statements correctly identifies what has happened? [K2]
The application failed due to a defect in the purchase identification module. This defect could have been caused by a programmer mistake or an error in the specification. The incorrect counting of purchase attempts indicates a flaw in the logic or implementation of the module responsible for identifying successful purchases.
Top of Form
Bottom of Form
To test a function, the programmer has to write a _________, which calls the function to be tested and passes it test data:
A driver is a piece of code that calls a function or module to be tested and passes it the necessary test data. It is commonly used in bottom-up integration testing to simulate the higher-level modules that invoke the function being tested. Stubs, on the other hand, are used to simulate lower-level modules. Reference: ISTQB CTFL Syllabus V4.0, Section 4.3.1.
Which of the following describes structure-based (white-box) test case design techniques?
Structure-based (white-box) test case design techniques involve deriving test cases systematically from the delivered code. The ISTQB CTFL syllabus v4.0 describes that these techniques focus on the internal structure of the software, using knowledge of the code to create test cases that ensure comprehensive coverage of the code's pathways and logic.
