iSQI ISTQB Certified Tester Foundation Level CTFL_Syll2018 Exam Questions

Answer : A

A unit test framework tool is a tool that supports the creation, execution and reporting of unit tests, which are tests that verify the functionality and quality of individual functions or methods in source code. A unit test framework tool can detect defects such as syntax errors, logic errors, boundary violations, etc.

Answer : A

25, 30, and 40 are the test data that show equivalence partitioning to verify if a customer is in their thirties or not. Equivalence partitioning is a technique to divide the input domain into partitions that are expected to behave similarly or produce the same output.Each partition should have at least one representative value as a test case1explains this as follows:

Equivalence Partitioning (or Equivalence Class Partitioning) is an software testing technique that divides the input data of a software unit into partitions of equivalent data from which test cases can be derived. In principle, test cases are designed to cover each partition at least once.

The fundamental concept of Equivalence Partitioning is that you can find more errors in a test case by using a representative value from an equivalence class than by using any other value from the class.

The input domain for the age parameter can be divided into four partitions: less than or equal to zero, between one and 29, between 30 and 39, and greater than or equal to 40. The first and the last partitions are invalid, as they are outside the range of possible ages for human beings. The second and the third partitions are valid, as they are within the range of possible ages for human beings. The test data 25, 30, and 40 represent one value from each partition, covering both valid and invalid cases.

B, C, and D are incorrect answers. B does not include a representative value from the invalid partition greater than or equal to 40. C does not include a representative value from the invalid partition less than or equal to zero. D does not include a representative value from the valid partition between one and 29.

Answer : A

Both functional and structural approaches are used in integration tests.Functional testing verifies that the integrated components work together as expected, while structural testing checks the internal structure and logic of the integrated components1explains this in more detail:

Integration testing is a level of software testing where individual units are combined and tested as a group. The purpose of this level of testing is to expose faults in the interaction between integrated units. Test drivers and test stubs are used to assist in Integration Testing.

Integration testing can be done in two ways:

Bottom-up Integration Testing: Bottom up integration testing begins with unit testing, followed by tests of progressively higher-level combinations of units called modules or builds.

Top-down Integration Testing: In top down integration testing, the highest-level modules are tested first and progressively lower-level modules are tested after that.

Answer : A

A dynamic analysis tool is the most effective tool for detecting memory leaks, which are defects where a code component fails to release memory after it has finished using it.A dynamic analysis tool monitors the behaviour of the software under test during execution and can measure memory usage, identify memory allocation errors, and report memory leaks13. The other options are not relevant tools for detecting memory leaks.A monitoring tool can measure the performance and resource consumption of the software under test, but it cannot identify memory leaks specifically13.A configuration management tool is used to manage the versions and changes of the software under test and its related artefacts, but it has nothing to do with memory leaks1.A coverage measurement tool is used to measure how much of the code or functionality of the software under test has been exercised by the test cases, but it cannot detect memory leaks1.

Answer : D

Mr; Mrs.; Ms; any other input is the correct list of the equivalence classes of the input values for this field. Equivalence partitioning is a technique to divide the input domain into partitions that are expected to behave similarly or produce the same output.Each partition should have at least one representative value as a test case3explains this as follows:

Equivalence Partitioning (or Equivalence Class Partitioning) is an software testing technique that divides the input data of a software unit into partitions of equivalent data from which test cases can be derived. In principle, test cases are designed to cover each partition at least once.

The fundamental concept of Equivalence Partitioning is that you can find more errors in a test case by using a representative value from an equivalence class than by using any other value from the class.

The input domain for this field can be divided into four partitions: Mr, Mrs., Ms, and any other input. The first three partitions are valid, as they are the only acceptable values for this field. The last partition is invalid, as it includes any value that is not Mr, Mrs., or Ms, such as Dr, Prof, Miss, etc.

Answer : D

A key difference between a peer review of code and static analysis of code using a tool is that static analysis targets the code technically whereas peer review is applicable to further aspects. Static analysis focuses on the technical aspects of the code, such as syntax, logic, complexity, quality, security, etc. Peer review can also address these aspects, but it can also consider other aspects, such as readability, maintainability, usability, functionality, etc. Peer review can also provide feedback, suggestions, or opinions from different perspectives or expertise levels. compares these two techniques as follows:

Static analysis tools are software tools that examine (analyse) source code without executing it. They are used by developers as part of their development environment for checking their code against coding standards (rules), finding syntax errors etc.

Peer reviews are manual checking activities where work products such as requirements specifications or code are examined by colleagues (peers) for defects.

A, B, and C are incorrect answers. A peer review does not find defects while static analysis finds failures (A), as both techniques can find defects but not failures. Failures are observed at runtime when executing the code. Peer reviews cannot find missing requirements whereas static analysis can (B), as both techniques cannot find missing requirements but only check conformance to existing requirements. Missing requirements can be found by other techniques such as elicitation or validation. A peer review finds failures while static analysis finds defects , as both techniques find defects but not failures. Failures are observed at runtime when executing the code.

Answer : D

Load testing tool checks for time response and resource utilization of a system under a specific load condition or scenario. Load testing tool can simulate multiple users accessing or performing operations on a system concurrently and measure how long it takes for the system to respond and how much CPU, memory, disk or network resources are consumed by the system.