iSQI CTFL_Syll2018 Exam Questions

The correct answer is D, as it describes tools that support reviews.Tools that support reviews are tools that assist with performing static testing activities such as checking documents for defects or compliance with standards3. Examples of tools that support reviews are:

Tools for document review and annotation

Tools for document comparison and version control

Tools for checklist management and defect tracking

Option A is incorrect, as it describes tools that support usability testing.Tools that support usability testing are tools that assist with performing dynamic testing activities related to how easy and user-friendly the software product is3. Examples of tools that support usability testing are:

Tools for recording user actions and feedback

Tools for analyzing user behavior and satisfaction

Tools for simulating different user interfaces and devices

Option B is incorrect, as it describes tools that assess data quality.Tools that assess data quality are tools that assist with evaluating and improving the accuracy and completeness of data used for testing3. Examples of tools that assess data quality are:

Tools for data validation and verification

Tools for data cleansing and transformation

Tools for data profiling and analysis

Option C is incorrect, as it describes tools that support specialized testing needs.Tools that support specialized testing needs are tools that assist with performing dynamic testing activities related to specific domains or technologies3. Examples of tools that support specialized testing needs are:

Tools for security testing

Tools for performance testing

Tools for accessibility testing

The correct answer is A, as it provides the highest level of boundary coverage using two-point boundary value analysis.Boundary value analysis is a black-box test technique that focuses on the boundaries of input and output partitions1.Two-point boundary value analysis is a variation of boundary value analysis that uses only two values for each boundary: one just below the boundary and one just above the boundary1. In this case, the boundaries are the balance ranges that correspond to different interest rates. Option A covers all four boundaries using two values for each boundary: $100.00 and $100.01 for the first boundary, $500.00 and $500.01 for the second boundary, $1,000.00 and $1,000.01 for the third boundary, and $5.00 as an invalid value below the lowest boundary. Option B covers only three boundaries using one value for each boundary: $100.00 for the first boundary, $500.00 for the second boundary, and $1,000.00 and $1,000.01 for the third boundary. Option C covers only two boundaries using three values for each boundary: $100.00, $100.01, and $100.02 for the first boundary, and $500.00 and $999.99 for the second boundary.Option D covers only two boundaries using one value for each boundary: $100.00 for the first boundary, and $1,000.01 for the third boundary, and $5.00 as an invalid value below the lowest boundary. Reference:1, Section 4.2.3

After completing the tool selection and a successful proof-of-concept, introducing the selected tool into an organization generally starts with a pilot project, which has the following objectives12:

Gaining in-depth knowledge about the tool, understanding both its strengths and weaknesses

Evaluating how the tool fits with existing processes and practices, and determining what would need to change

Assessing whether the benefits will be achieved at reasonable cost

Identifying and resolving any technical and organizational issues before deploying the tool on a larger scale

Providing training, coaching, and mentoring for users of the tool

Defining metrics to measure the success of the tool deployment

Therefore, the option D is the most typical objective of running a pilot project, as it is essential to ensure the compatibility and suitability of the tool with the current way of working, and to identify any potential risks or challenges that may arise from the tool introduction12.

The other options are not typical objectives of running a pilot project, because they are either part of the tool selection process, or the outcomes of the pilot project. They are:

To establish whether the tool is available for a free trial period (and for how long) (A).This is part of the tool selection process, which involves gathering information about the tool features, costs, support, and availability12.This should be done before running a pilot project, as it helps to narrow down the list of potential tools and to conduct a proof-of-concept12.

To provide training, coaching, and mentoring for users of the tool (B).This is an outcome of the pilot project, which aims to increase the competence and confidence of the tool users and to facilitate the tool adoption12.This should be done during and after the pilot project, as it helps to ensure the effective and efficient use of the tool and to address any issues or feedback from the users12.

To develop a clear set of requirements and objective criteria against which the tool can be evaluated .This is also part of the tool selection process, which involves defining the tool requirements based on the needs and expectations of the stakeholders, and establishing the evaluation criteria based on the benefits and risks of the tool12.This should also be done before running a pilot project, as it helps to compare and rank the potential tools and to select the most suitable one12.

ISTQB Foundation Level 2018 syllabus

Chapter 6 - Tool Support for Testing | PPT

A test completion report for a test level typically includes a summary of all the testing activities that have been performed. It should detail any deviations from the original test schedule, including any changes in the planned duration or effort that were required to complete the test activities. This report serves as a record of what was tested, how it was tested, and any issues that were encountered.

Priority is an important item of information that is missing from the incident report. Priority indicates the importance or urgency of resolving the incident, based on the business needs and the impact on the stakeholders. Priority is usually assigned by the project manager or the customer, and it helps to determine the order in which incidents should be addressed. Priority may differ from severity, which indicates the degree of impact of the incident on the system or the component under test. Severity is usually assigned by the tester or the developer, and it helps to assess the risk of the incident. For example, an incident may have a high severity but a low priority, if it affects a critical function but only occurs in a rare situation. Conversely, an incident may have a low severity but a high priority, if it affects a minor function but occurs frequently or affects many users. Therefore, both priority and severity are useful information for incident management and resolution.

The other options are not essential information for the incident report, although they may be helpful or desirable in some cases. Recommendations are suggestions or proposals for resolving the incident, which may be provided by the tester, the developer, or other stakeholders. However, recommendations are not mandatory, and they may not be feasible or acceptable in some situations. Name of tester is the identifier of the person who reported the incident, which may be useful for communication or accountability purposes. However, name of tester is not critical, and it may be replaced by other identifiers, such as email address, employee number, or role. Change history is the record of the changes made to the incident report, such as status, resolution, or comments. Change history is valuable for tracking and auditing purposes, but it is not part of the initial incident report, rather it is updated as the incident progresses.