CTFL_Syll2018 Exam Dumps - ISTQB Certified Tester Foundation Level (Syllabus 2018)

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.

In a Scrum development life cycle model, regression testing is an increasingly important activity as the project progresses. Scrum is an agile framework that follows an iterative and incremental approach to software development, where the software is delivered in small units called sprints. Regression testing is a type of testing that verifies that previously tested software still performs as expected after changes or modifications. Regression testing is essential in Scrum, as new features or functionalities are added or modified in each sprint, which can introduce new defects or affect existing ones. Therefore, regression testing should be performed at the end of each sprint, as well as before releasing the software, to ensure that the software meets the quality standards and user expectations.

References: Certified Tester Foundation Level Syllabus, Section 5.3.2

The test execution schedule that meets the test plan requirements and logical dependencies is e, a, d, c, b. This schedule follows the order of re-tests first (e), followed by the highest priority tests (a and d), and then creates test data for subsequent tests (c and b). This schedule also respects the logical dependencies, as test case a creates an admin user, which is necessary for test case d to create a standard user, which is necessary for test cases c and b to perform other actions1 .

Cost can be regarded as an exit criterion, as it is one of the factors that can influence the decision to stop testing. Spending too much money on testing will result in an unprofitable product, and having cost as an exit criterion helps avoid this. The other options are incorrect, as the financial value of product quality can be estimated, the cost of testing can be measured effectively, and having cost as an exit criterion does not necessarily constrain the testing project or help achieve the desired quality level.

References: Section 2.2.1, Section 2.2.3

100% branch coverage means 100% statement coverage, but not vice-versa. Branch coverage is a stronger criterion than statement coverage, as it requires that every possible outcome of each decision point is executed at least once. Statement coverage only requires that every executable statement is executed at least once1 explains this as follows:

Branch Coverage (also known as Decision Coverage) measures which possible branches in flow control structures are followed. Branch Coverage is a testing method, which aims to ensure that each one of the possible branch from each decision point is executed at least once and thereby ensuring that all reachable code is executed.

Statement Coverage measures the number of statements in the source code that are executed during the test. Statement Coverage is a metric, which is used to calculate and measure the number of statements in the source code which have been executed during testing.

B, C, and D are false statements. 100% statement coverage does not mean 100% branch coverage (B), as there may be some branches that are not covered by the test cases. 100% branch coverage does not mean 100% statement coverage and vice-versa ©, as branch coverage implies statement coverage but not the other way around. It is possible to achieve 100% statement coverage (D), but it may not be feasible or cost-effective for some systems.

According to the syllabus, non-functional testing is a type of software testing that verifies non-functional aspects or attributes of a software product or system, such as performance, usability, reliability, security, etc. Non-functional testing evaluates how well a system operates or behaves under certain conditions or scenarios, rather than what functions or features it provides. The answer D is correct because it best exemplifies non-functional testing. Tests which capture the time it takes to save a file are examples of performance testing, which is a type of non-functional testing that measures how fast or responsive a system is under various workloads or situations. The other answers are incorrect because they exemplify functional testing or structural testing, which are not types of non-functional testing. Tests based on the internal structure of a component or system (A) are examples of structural testing, which is a type of software testing that verifies the implementation or code of a software product or system. Tests related to ‘what’ the system should do (B) are examples of functional testing, which is a type of software testing that verifies the functionality or behavior of a software product or system. Tests which calculate overtime pay for those employees entitled to such © are also examples of functional testing, as they verify a specific function or feature of a software product or system.

References: Certified Tester Foundation Level Syllabus, Section 1.2.1, page 10-11.

A walkthrough is lead by a moderator and requires pre-meeting preparation and post meeting follow up is the statement that is not true about walkthroughs, because it describes a different type of review called inspection . A walkthrough is a type of informal review that involves the author of a document presenting it to a group of peers or stakeholders to establish a common understanding and to find possible defects . A walkthrough does not have a moderator, but rather an author who leads the review. A walkthrough does not require pre-meeting preparation or post meeting follow up, but rather relies on the author’s knowledge and skills . The other options are true statements about walkthroughs. Option B is true, because a walkthrough may take the form of scenarios, dry runs and peer group review, depending on the type and purpose of the document being reviewed . Option C is true, because the purpose of a walkthrough is to establish common understanding of a document and to find possible defects in it . Option D is true, because pre-meeting preparation, documentation and distribution of results are optional for a walkthrough, as they depend on the author’s discretion and preference .

Code coverage can be used to ensure that all code is exercised by tests, because it measures how much of the code or functionality of the software under test has been exercised by the test cases . Code coverage can help to identify untested or dead code, improve test design, and assess test quality . The other options are not true statements about code coverage. Option A is false, because 100% code coverage does not imply 100% coverage of requirements, as there may be defects or gaps in the requirements or in the mapping between requirements and code . Option B is false, because 100% code coverage does not guarantee that there are no coding errors, as there may be logical or functional errors that are not detected by code coverage . Option D is false, because code coverage does not ensure that all decisions are correctly implemented in the code, as it only measures whether the decisions are executed or not, but not whether they produce the correct results .