Pass the ISTQB Foundation Level CTFL-Foundation Questions and answers with ExamsMirror

Boundary value testing focuses on testing at the boundaries between partitions. It tests conditions on, below, and above the edges of input and output equivalence classes to identify defects that occur at the boundaries. This technique is different from equivalence partitioning, which divides input data into partitions but does not specifically target boundary conditions. Reference: ISTQB CTFL Syllabus V4.0, Section 4.2.1​​.

Quality in software testing is best defined as conformance to requirements. The ISTQB CTFL syllabus v4.0 states that quality is the degree to which a component, system, or process meets specified requirements and/or user/customer needs and expectations​​.

For reviewing safety-critical components in a software project, the most adequate review types are Inspections and Technical Reviews. Inspections are a formal review technique with a well-defined process that includes thorough preparation, examination, and documentation, making them suitable for critical components. Technical Reviews involve a detailed examination of the technical aspects of the software and are conducted by experts, which ensures that any potential issues are identified and addressed early.

It is unlikely that developers will have a better understanding of the requirements than testers, partly because testers work closely with the user community (and may be drawn from it) and partly because developers seldom work with the complete set of requirements in a medium to large development.

Testers may raise incidents related to the difference between user expectations and the specification, but these are not unnecessary. Such issues are more likely to arise at the later stages of testing.

Early testing (unit testing) is usually done most effectively by developers with a good understanding of the code and the development environment; they can be more efficient andmore effective at this level. Later independent stages of testing offset any disadvantage from the lack of independence at unit testing level.

Exit criteria are defined to determine when a specific testing activity or the entire testing process should be considered complete. This includes setting conditions such as when to stop testing, the end of a test level, and when certain pre-defined conditions or coverage levels have been achieved. Exit criteria help ensure that testing is systematic and meets the project's quality standards before moving on to the next phase or release​​.

The impossibility of complete testing has several important consequences. It means we can never be certain that the program is entirely bug-free (A). There is no definite stopping point for testing, which can make it easier for some managers to justify minimal testing (B). Additionally, there is no simple answer for which testing tasks should always be required, as each task takes time that could be allocated to other critical activities (C). Therefore, all these consequences (D) are valid and important considerations in software testing. Reference: ISTQB CTFL Syllabus V4.0, Section 2.2​​.

Non-functional requirements define how the system performs a certain function, rather than specific behaviors or functions of the system. Security, performance, usability, reliability, and maintainability are common examples of non-functional requirements. Ensuring the security of customer details is a non-functional requirement because it specifies a quality attribute that the system must have. Reference: ISTQB CTFL Syllabus V4.0, Section 4.1​​.

Walkthroughs are often led by the author of the document and are used to aid learning and understanding among team members. These informal review meetings help in discussing the content and obtaining feedback from participants, but they are less formal than inspections and do not necessarily involve defined roles for all participants or result in documented outcomes. Reference: ISTQB CTFL Syllabus V4.0, Section 3.2.1​​.

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 thatinvoke 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​​.

Checking test logs against the exit criteria specified in test planning is not a major task of test implementation and execution. This activity is more related to evaluating exit criteria and reporting. Major tasks of test implementation and execution include developing and prioritizing test cases, creating test data, writing test procedures, optionally preparing test harnesses, and writing automated test scripts, logging the outcome of test execution, and verifying that the test environment has been set up correctly​​.