CTFL_Syll2018 Exam Dumps - iSQI CTFL2018 Questions and Answers

Test plan is the test document where you would expect to find test exit criteria described. Test exit criteria are the conditions or requirements that must be met before testing can be completed or stopped. Test exit criteria are usually defined during test planning and control phase and evaluated during evaluating exit criteria and reporting phase. Test plan is a document that describes the scope, approach, resources, schedule, risks, metrics etc., for testing activities. Test plan also includes test exit criteria as part of its contents3 defines test exit criteria and test plan as follows:

Test exit criteria: The set of generic or specific conditions for permitting process exit criteria that are defined for each Test Level.

Test plan: A document describing the scope, approach, resources and schedule of intended test activities.

Component testing is a part of the V-Model, which is a development life cycle model that shows the relationship between each phase of development and its corresponding phase of testing. In this model, each level of testing (unit testing, integration testing, system testing, acceptance testing) has a corresponding level of development (component design, component integration, system design, requirements analysis). Component testing is the process of testing individual components or units of software in isolation from other components or systems. Component testing verifies that the components meet their functional and non-functional requirements and work as expected in their intended environment. Component testing is usually done by developers who have access to the component design and code specifications. You can find more information about component testing and the V-Model in Software Testing Foundations: A Study Guide for the Certified Tester Exam, Chapter 22.

Functional and Structural tests are two different test design techniques, not test levels or test types. They can be applied at any test level (Unit, Integration, System, Acceptance) and for any test type (Functional, Non-functional, Regression, Maintenance). Therefore, option A is the correct answer. Option B is incorrect because Functional tests can be performed at any test level, not just Unit and Integration. Option C is incorrect because Functional and Structural are not test levels, but test design techniques. Option D is incorrect because Structural tests can be performed at any test level, not just Unit.

References: ISTQB Certified Tester Foundation Level Syllabus 2018 v3.1.1, Chapter 4.1.2 Test Design Techniques1

Test implementation and execution is the stage of the Fundamental Test Process where testers write detailed steps for executing each test case (test procedures), prepare and prioritize test cases for execution, execute test cases and record results, compare actual results with expected results and report discrepancies as incidents.

Traceability between the test basis and test work products means that there is a clear and documented relationship between the requirements, design, and other sources of test conditions, and the test cases, test procedures, and test results that are derived from them. This helps to ensure that the test work products are consistent, complete, and relevant to the test basis. One of the direct benefits of maintaining traceability is the ability to analyse the impact of changes in the test basis on the test work products, and vice versa. For example, if a requirement is changed, added, or deleted, traceability can help to identify which test cases, test procedures, and test results need to be updated, executed, or removed accordingly. Similarly, if a test result reveals a defect in the test basis, traceability can help to locate the source of the defect and determine the scope of the correction. Traceability also supports other benefits, such as measuring test coverage, reporting test progress, and evaluating test quality, but these are not direct benefits of maintaining traceability, rather they are outcomes of using traceability information for various purposes. References: ISTQB Certified Tester Foundation Level Syllabus v4.0, Chapter 3.1.2, p. 23-24 1; ISTQB Glossary v4.0, p. 67 2

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

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 .

Component testing is concerned with testing the smallest bodies of software, such as functions, classes, procedures, or modules. Component testing is also known as unit testing or module testing. Feature testing is a type of functional testing that focuses on verifying a specific feature or functionality of a system. Functional testing is a type of black-box testing that verifies that the system meets its functional requirements and specifications. Subsystem testing is a type of integration testing that verifies that a group of components work together as expected. References: ISTQB Certified Tester Foundation Level Syllabus 2018, Section 2.2

Regression testing is intended to find side-effects after changes have been applied to the system under test. Side-effects are unintended consequences of changes that may cause new defects or re-introduce previously fixed defects in parts of the system that were not directly modified. Regression testing can be done at any level of testing and can use any type of testing technique.

The statement that incidents cannot be raised during development is not true, because incidents can be raised during any stage of software development life cycle where deviations from expected or desired behaviour are observed . Incidents can be raised during development, review, testing or use of a software product . The other options are true statements about incidents.