ISTQB CTFL-2018 Practice Test - Questions Answers, Page 20

The goal of statement testing is to increase the percentage of executable statements that are exercised by a test set.This is also known as statement coverage or line coverage3defines this as follows:

Statement Coverage (also known as Line Coverage) measures how many statements have been executed by your tests. It's calculated by dividing the number of executed statements by total number statements in source code file.

Statement testing does not aim to reduce the number of tests needed to test the system (A), assess the correctness of key statements in each module of the application (B), or assess the number of code statements needed to implement each feature (D).

Agile development can be classified as an iterative incremental life cycle model, where each iteration delivers a working product increment that can be evaluated by stakeholders and users. describes this as follows:

Iterative Incremental Development Model is a process where creating requirements, designing, building and testing a system in small parts. This model divided into small parts which will help to make modules very easily.In this model, module passes through some phases like requirements, coding, designing, testing.

Agile Model mostly recommended to use for current software development industries because it is very realistic approach to develop any kind of software.It follows iterative approach which means whole project divided into small iterations or modules.

Agile development is not related to any life cycle model (A), RAD (B), or V model .

It is a project risk since successful completion of the project depends on successful and timely completion of the tests. defines project risks as follows:

Project risks are risks that affect the project schedule, resources, or budget. They can be related to the project management process, such as planning, estimation, communication, or monitoring. Project risks can also be related to external factors, such as dependencies, stakeholders, vendors, or regulations.

It is not a product risk (B and C), as product risks are risks that affect the quality or performance of the software product. defines product risks as follows:

Product risks are risks that affect the functionality, reliability, usability, efficiency, maintainability, or portability of the software product. They can be related to the software requirements, design, implementation, or testing. Product risks can also be related to user expectations, needs, or satisfaction.

It is not no longer a risk for the Test Manager (D), as the sub-contractor's failure may still impact the Test Manager's responsibilities and deliverables. The Test Manager should monitor and mitigate this risk as much as possible.

(0, 12, 13,18,19) represent boundary values for the age groups. Boundary value analysis is a technique to test the values at the boundaries of an input domain or equivalence partition. explains this as follows:

Boundary value analysis (BVA) is based on testing the boundary values of valid and invalid partitions. The behavior at the edge of each equivalence partition is more likely to be incorrect than the behavior within the partition, so boundaries are an area where testing is likely to yield defects.

(-1,0,11,12,13,14,18,19) (B) are not boundary values, but include some boundary values and some non-boundary values. (4,5,15,20) are not boundary values at all. (-1.0,12,13,18,19) (D) are not boundary values either, as -1.0 is not an integer value.

For the code fragment given below, one test case is required for statement coverage and two test cases are required for branch coverage. Statement coverage requires that every executable statement in the code is executed at least once. Branch coverage requires that every possible outcome of each decision point in the code is executed at least once. The following table shows how to achieve statement and branch coverage for the code fragment:

Test Case

Input

Output

Statement Coverage

Branch Coverage

1

x = 3

y = 9

S1, S2, S3

T1 = true

2

x = 5

y = 25

S1, S2

T1 = false

As shown in the table, test case 1 covers all three statements (S1, S2, S3) in the code fragment, achieving 100% statement coverage. Test case 2 covers only two statements (S1, S2) in the code fragment, but it exercises a different outcome of the decision point T1 (if x < 4), achieving 100% branch coverage.

II, II,I, and V are true statements about test reports. Test reports shall give stakeholders information as basis for decisions (II,), as they provide an overview of the test results, the test coverage, the remaining risks, and the recommendations for the next steps. Test reports shall summarize what happened through a period of testing (II,I), as they describe the test activities, the test objectives, the test methods, the test environment, and the test incidents.Test reports shall include information about remaining risks (V), as they identify the areas of uncertainty or potential failure that may affect the quality or performance of the system under test1defines a test report as follows:

A test report is a document that summarizes and communicates the outcomes of testing to stakeholders. A test report typically includes the following information:

Test summary: A brief overview of the testing process, including the scope, objectives, approach, and results.

Test evaluation: An evaluation of the testing process against the exit criteria and quality standards, including the test coverage, defect status, and risk assessment.

Test conclusion: A conclusion on the suitability of the system under test for release or deployment, based on the test results and evaluation.

Test recommendations: A recommendation on the actions to be taken after testing, such as fixing defects, conducting further testing, or implementing improvements.

I and IV are false statements about test reports. Test reports shall not be approved by the test team (I), as they are usually approved by a higher authority or a designated stakeholder who has the responsibility and authority to make decisions based on the test report. Test reports shall not be approved by the development team, the test team and the customer (IV), as this may cause conflicts of interest or delays in decision making.

It is not allowed as organizations can't change the test levels as these are chosen on the basis of the SDLC (software development life cycle) model. The V-model is a type of SDLC model that defines four test levels: component testing, integration testing, system testing, and acceptance testing. Each test level corresponds to a development phase in a parallel manner.Integration testing is an essential part of the V-model, as it verifies that the components work together correctly and consistently2explains this as follows:

The V-model is a graphical representation of a systems development lifecycle. It is used to produce rigorous development lifecycle models and project management models. The V-model falls into three broad categories, the German V-Modell, a general testing model and the US government standard.

The V-model summarizes the main steps to be taken in conjunction with the corresponding deliverables within project execution and delivery. It describes software development activities from requirements specification to maintenance.

The V-Model demonstrates the relationships between each phase of the development life cycle and its associated phase of testing.

A, C, and D are incorrect answers. A implies that integration testing is not an important test level and can be dispensed with, which is not true as integration testing ensures that the system functions as a whole and meets its requirements. C implies that organizations can decide on which test levels to do depending on the context of the system under test, which is not true as test levels are determined by the chosen SDLC model and its objectives. D implies that integration testing is a very important test level and ignoring it means definite poor product quality, which is true but not relevant to why it is not allowed to do away with integration testing in a V-model.

Regression testing is testing of an already tested program after modification to discover any defects introduced or uncovered as a result of changes in software or its environment.Regression testing ensures that previously working functionality still works after changes are made3defines regression testing as follows:

Regression Testing is defined as a type of software testing to confirm that a recent program or code change has not adversely affected existing features.

Regression Testing is nothing but full or partial selection of already executed test cases which are re-executed to ensure existing functionalities work fine.

I, II,I, IV, and V are incorrect statements about regression testing. Retesting of a fixed defect (I) is not regression testing, but confirmation testing or rework testing, which verifies that a specific defect has been resolved. Testing of new functionality in a program (II,I) is not regression testing, but functional testing or new feature testing, which verifies that new requirements are met by new code. Regression testing applies only to functional testing (IV) is not true, as regression testing can also apply to non-functional aspects such as performance or security. Tests that do not have to be repeatable, because they are only used once (V) are not regression testing, but exploratory testing or ad hoc testing, which are based on learning and discovery rather than predefined test cases.

Introducing the tool to all the test teams of the organization at the same time is a factor that could negatively influence the success of the deployment of a tool within an organization, as it may cause resistance, confusion, or overload among the test teams. A better approach would be to introduce the tool gradually and incrementally, starting with a pilot project or a small group of users, and then expanding to other test teams based on the feedback and results. suggests this as follows:

A pilot project should be conducted before introducing a new test tool into an organization in order to learn more about how to use it effectively and efficiently in your context and how it will interact with other tools and processes. A pilot project should involve a small group of users who are willing and able to experiment with the tool and provide feedback. The pilot project should have clear objectives, scope, duration, and success criteria.

B, C, and D are factors that could positively influence the success of the deployment of a tool within an organization. Collecting usage information of the tool from the early projects (B) can help to evaluate the benefits and drawbacks of the tool, identify areas for improvement, and justify the investment. Providing training and coaching for new users of the tool can help to increase their confidence and competence in using the tool, reduce errors and frustration, and enhance their productivity and satisfaction. Adapting and improving the processes to the usage of the tool (D) can help to optimize the workflow and performance of the test teams, align the tool with the organizational goals and standards, and increase the value and quality of the testing activities.