Pass the iSQI CTFL2018 CTFL_Syll2018 Questions and answers with CertsForce

The question asks which of the test cases will ensure that the statement ‘Print ‘Hold’’ is exercised. The statement ‘Print ‘Hold’’ is executed when X > Y and Z < Y. Therefore, to exercise this statement, we need to choose a test case that satisfies these conditions. Among the options given in this question, only C satisfies these conditions. X = 42 > Y =43 and Z =42 < Y =43. Therefore, C is the correct answer.

Planning and control, analysis, design, implementation, execution, evaluation of exit criteria and reporting, test closure. The fundamental test process is a generic model that describes the main activities and tasks involved in testing. The fundamental test process consists of five phases: planning and control, analysis and design, implementation and execution, evaluation of exit criteria and reporting, and test closure activities. Each phase has specific objectives, inputs, outputs, and deliverables. A detailed explanation of the fundamental test process can be found in A Study Guide to the ISTQB® Foundation Level 2018 Syllabus, pages 13-241.

The main reason for using a pilot project to introduce a testing tool into an organization is C. To assess whether the tool will be cost-effective. A pilot project is a small-scale trial or experiment that is used to evaluate the feasibility, benefits, risks, and challenges of introducing a testing tool into an organization. A pilot project can help to assess whether the tool will be cost-effective, by comparing the costs of acquiring, deploying, using, and maintaining the tool with the benefits of using the tool, such as increased efficiency, effectiveness, quality, etc. A pilot project can also help to identify any technical, organizational, or human factors that may affect the successful adoption of the tool, and plan for any necessary actions or changes to address them. A detailed explanation of pilot projects can be found in A Study Guide to the ISTQB® Foundation Level 2018 Syllabus, pages 115-1161.

A valid reason for writing test cases based on experience and intuition is C. Tests based on experience and intuition can supplement formal techniques. Experience and intuition are valuable sources of test ideas that can help testers to identify potential risks, errors, or scenarios that may not be covered by formal techniques. Formal techniques are systematic methods that use rules or algorithms to derive test cases from the test basis (such as specifications, code, etc.). Formal techniques include black-box techniques (such as equivalence partitioning, boundary value analysis, etc.) and white-box techniques (such as statement coverage, decision coverage, etc.). Formal techniques can provide a high level of coverage and consistency, but they may not be able to capture all possible situations or behaviors of the system or component under test. Therefore, tests based on experience and intuition can supplement formal techniques by adding more diversity and creativity to the test cases. A detailed explanation of experience-based testing techniques can be found in [A Study Guide to the ISTQB® Foundation Level 2018 Syllabus], pages 74-76.

To be based on an analysis of the structure of the component or system. White box testing techniques are based on the internal structure and code of the system, not on its specifications or functionality. White box testing techniques include statement coverage, decision coverage, branch coverage, path coverage, etc. White box testing techniques are usually performed at lower levels of testing, such as unit testing or component testing. A detailed explanation of white box testing techniques can be found in [A Study Guide to the ISTQB® Foundation Level 2018 Syllabus], pages 68-74.

 Functional testing to test security at the system level, load testing at the system level to ensure the system availability is acceptable, regression testing at all levels, structure based testing at the component level only are the test types that will be required during the development1. A bank is developing a new service that will be delivered via the web. The user interactions are defined as a set of use cases and the service is designed to be available continuously 24/7. In view of the challenging characteristics of the service, the test manager has decided that the code should be thoroughly tested at component level. Therefore, the following test types will be required during the development:

Functional testing to test security at the system level: This type of testing verifies that the software product performs its intended functions according to the user requirements and expectations1. Security is one of the functional aspects that needs to be tested at the system level, as it ensures that the software product protects itself from unauthorized access or harm1.

Load testing at the system level to ensure the system availability is acceptable: This type of testing verifies that the software product can handle the expected or peak load of users or transactions without degrading its performance or functionality1. Availability is one of the quality attributes that needs to be tested at the system level, as it measures how well the software product performs its intended functions under specified conditions without interruption or failure1.

Regression testing at all levels: This type of testing verifies that previously tested software still performs correctly after changes or defect corrections1. Regression testing is required at all levels of testing, as changes or defect corrections can introduce new defects or affect existing functionality1.

Structure based testing at the component level only: This type of testing uses the structure or logic of the source code as a test basis to derive test cases and measure test coverage1. Structure based testing is required at the component level only, as the test manager has decided that the code should be thoroughly tested at component level to ensure its quality and reliability1.

 Likelihood of failure = 10%, potential cost of impact = $500,000. The level of risk to the project can be calculated by multiplying the likelihood of failure by the potential cost of impact. This gives us the following values for each option:

A. 1% x $1m = $10,000 B. 10% x $500,000 = $50,000 C. 20% x $150,000 = $30,000 D. 5% x $500,000 = $25,000

The statement that environmental conditions only affect the hardware - not the software is not a good explanation why software failures can be caused by environmental conditions. Environmental conditions can affect both the hardware and the software, as they can influence the performance, reliability, and functionality of the system. For example, factors like magnetism, radiation, pollution, heat, humidity, vibration, etc. can affect electronic devices and the embedded software that runs on them. Software failures caused by environmental conditions can have serious consequences, especially for safety-critical systems. References: Certified Tester Foundation Level Syllabus, Section 1.2.2

A test case is a set of preconditions, inputs, actions, expected results and postconditions developed based on test conditions. A test condition is a statement about what to test in terms of measurable coverage criteria from analysis of the test basis. A test plan is a description of the test objectives to be achieved and the means and the schedule for achieving them. A test oracle is a source to determine expected results to compare with the actual result of the system under test.

References: Certified Tester Foundation Level Syllabus, Section 4.2.1 and Glossary

2-point boundary value analysis is a technique that tests the boundary values of valid and invalid partitions with two values each: one at the boundary and one just outside the boundary. For example, if the valid range is 1 to 10, the 2-point boundary values are 1, 2, 9, 10 for the valid partition, and 0, 11 for the invalid partitions. The advantage of this technique is that it reduces the number of test cases compared to 3-point boundary value analysis, which tests one value inside the boundary as well. However, it may miss some defects that occur only with the values inside the boundary.

In this question, the valid partitions are the ranges of spending that correspond to different discounts, and the invalid partitions are the ranges of spending that are below or above the valid partitions. The boundaries are the values of spending that trigger a change in the discount rate. The 2-point boundary values for each partition are:

Invalid partition below £500: £0, £499

Valid partition for 5% discount: £500, £501

Valid partition for 10% discount: £1000, £1001

Valid partition for 15% discount: £2000, £2001

Valid partition for 20% discount: £4000, £4001

Invalid partition above £4000: £4001, £4002

The test cases TC1 and TC2 already cover two of the boundary values: £500 and £2000. Therefore, to achieve 100% 2-point boundary value analysis, we need to write seven more test cases to cover the remaining boundary values: £0, £499, £501, £1000, £1001, £4000, and £4002. Note that £4001 is a boundary value for both the valid and invalid partitions, so we only need to test it once.

References: ISTQB Certified Tester Foundation Level Syllabus v4.0, Chapter 4.2.2, p. 35-36 1; ISTQB Glossary v4.0, p. 16 2; Software Testing - Boundary Value Analysis 2