Pass the iSQI CTFL2018 CTFL_Syll2018 Questions and answers with ExamsMirror

 According to the syllabus, the choice of a particular type of software development life cycle (SDLC) model depends on various factors, such as project size, complexity, scope, budget, schedule, quality requirements, risk level, customer involvement, etc. The type of product being developed is one of the most important factors that influences the selection of an SDLC model, as different products may have different characteristics, expectations, and challenges that require different approaches to development. For example, a product that has well-defined and stable requirements may benefit from a sequential SDLC model like waterfall or V-model, while a product that has vague or changing requirements may benefit from an iterative SDLC model like incremental or agile. The answer D is correct because it best reflects the reason for selecting a particular type of SDLC model. The other answers are incorrect because they are not good reasons for selecting a particular type of SDLC model. Tester skill level with the SDLC model (A) may affect the effectiveness and efficiency of testing activities, but it should not be the primary factor for choosing an SDLC model. Testers should be able to adapt to different SDLC models depending on the project context and objectives. The project manager’s preference (B) may reflect their personal experience or opinion, but it should not be the sole factor for choosing an SDLC model. The project manager should consider various factors and consult with other stakeholders before selecting an SDLC model. The project team’s overall familiarity with the model © may affect the productivity and collaboration of the team members, but it should not be the main factor for choosing an SDLC model. The project team should be able to learn and apply different SDLC models depending on the project context and objectives.

References: Certified Tester Foundation Level Syllabus, Section 1.1.1, page 9-10.

 Having the company’s independent test team design and execute the tests would achieve the highest level of testing independence for a project’s test level, because it would reduce the bias and influence of the developers or other stakeholders who are involved in the software development1 . An independent test team can provide a different perspective and focus on testing activities without being affected by development pressures or deadlines1 . The other options would not achieve the highest level of testing independence for a project’s test level. Option A is not a good option, because training developers to design good tests for the test team to execute would still introduce some bias and influence from the developers’ point of view1 . Option C is not a good option, because minimizing contact between testers and developers during test design to avoid bias would reduce the communication and collaboration that are essential for effective testing and defect resolution1 . Option D is not a good option, because outsourcing test design and execution to a different company would introduce some risks and challenges such as contractual issues, cultural differences, or loss of control over quality

Explanation of Correct Answer: A benefit of running tests with a test automation tool is that the time spent on repetitive tasks is reduced, as the tool can execute tests faster and more reliably than humans. Therefore, option D is correct. Option A is incorrect, as test coverage is not increased by using a test automation tool, but by designing more effective test cases. Option B is incorrect, as the number of found bugs is not reduced by using a test automation tool, but by improving the quality of the software under test. Option C is incorrect, as the total cost of the test project does not always decrease by using a test automation tool, as there are costs associated with developing and maintaining the automated tests.

References: Certified Tester Foundation Level Syllabus, Section 6.1

To cover 100% statement coverage, we need to execute every statement in the code at least once. To cover 100% decision coverage, we need to execute every branch in the code at least once. The minimum number of test cases required to achieve both statement and decision coverage is 4 for statement and 5 for decision. Here is one possible set of test cases:

| Test Case | Input | Output | Statement Coverage | Decision Coverage | | TC1 | Walking = True, Midnight = False, Raining = False, Running = False | Take umbrella | S1, S2, S3, S4, S5 | D1-T, D2-T | | TC2 | Walking = False, Midnight = True, Raining = False, Running = False | Search light | S1, S2, S6, S7 | D1-F, D3-T | | TC3 | Walking = False, Midnight = False, Raining = True, Running = False | Take umbrella and search light | S1, S2, S6, S8, S9 | D1-F, D3-F, D4-T | | TC4 | Walking = False, Midnight = False, Raining = False, Running = True | Keep doing what you were doing | S1, S2, S6, S8, S10 | D1-F, D3-F, D4-F |

b & c are debugging activities, because they involve locating the cause of failure and fixing the defect in the software . Debugging is the process of finding and removing the causes of software failures . The other options are not debugging activities, but rather testing activities. Option A is a testing activity, because it involves identifying a failure in the software by comparing the expected and actual results . Option D is a testing activity, because it involves checking the fix has resolved the failure by re-testing the software .

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

According to the syllabus, boundary value analysis is a technique that tests the values on and near the boundaries of an equivalence partition. The three-point boundary values are the minimum, just below the minimum, and just above the minimum for the lower boundary, and the maximum, just below the maximum, and just above the maximum for the upper boundary. The answer A is correct because it contains the three-point boundary values for both the lower and upper boundaries of the age range. The other answers are incorrect because they either miss some of the boundary values or include values that are too far from the boundaries.

References: Certified Tester Foundation Level Syllabus, Section 4.2.2, page 41.

A static analysis tool can be used by developers, testers and quality assurance personnel in looking for defects prior to dynamic testing, because it can analyse the code or design of the software under test without executing it and identify errors such as syntax errors, missing declarations, undefined variables, unused variables, or unreachable code . The other options are not tools that can be used by developers, testers and quality assurance personnel in looking for defects prior to dynamic testing. Option B is not a tool that can be used for this purpose, because a modeling tool is used to create graphical or textual representations of the software under test, such as state diagrams, data flow diagrams, or use cases . Option C is not a tool that can be used for this purpose, because a test data preparation tool is used to generate or manipulate data that are needed for executing the test cases or procedures . Option D is not a tool that can be used for this purpose, because a configuration management tool is used to manage and control the versions and changes of the software under test and the testware .

Traceability is the ability to identify related items in documentation and software, such as requirements, design specifications, code modules, test cases, test results, etc. Traceability helps to ensure that all requirements are covered by tests, that all tests are linked to requirements, and that any changes in requirements or software can be traced to their impact on other items.

 Boundary value analysis and decision table testing are the best choice of one black box technique and one white box technique for test case design2. A black box technique is a technique that uses the external behaviour or specification of a system as a test basis to derive test cases without referring to its internal structure or logic2. A white box technique is a technique that uses the internal structure or logic of a system as a test basis to derive test cases and measure test coverage2. In this question, the system has complex business rules and many branches in the structure of its code components. Therefore, we need to choose a black box technique that can handle complex business rules and a white box technique that can cover many branches.

Boundary value analysis is a black box technique that tests the values at or near the boundaries of an equivalence partition2. Boundary value analysis can handle complex business rules by identifying the boundary conditions that may cause errors or exceptions in the system’s behaviour2.

Decision table testing is a white box technique that tests all possible combinations of conditions and actions in a decision logic2. Decision table testing can cover many branches by creating a table that shows how each condition affects each action and then deriving test cases from each row of the table2.

Therefore, boundary value analysis and decision table testing are the best choice of one black box technique and one white box technique for test case design.