CTFL_Syll2018 Exam Dumps - iSQI CTFL2018 Questions and Answers

Less than 0, 1 to 80, more than 80 is a valid collection of equivalence classes for the following problem: “An Integer numeric field shall contain values from 1 to 80 both values inclusive”. Equivalence partitioning is a technique to divide the input domain into partitions that are expected to behave similarly or produce the same output. Each partition should have at least one representative value as a test case2 explains equivalence partitioning as follows:

Equivalence Partitioning (or Equivalence Class Partitioning) is an software testing technique that divides the input data of a software unit into partitions of equivalent data from which test cases can be derived. In principle, test cases are designed to cover each partition at least once.

The fundamental concept of Equivalence Partitioning is that you can find more errors in a test case by using a representative value from an equivalence class than by using any other value from the class.

The input domain for this problem can be divided into three partitions: less than 0, 1 to 80, and more than 80. The first and the last partitions are invalid, as they are outside the range of acceptable values for this field. The middle partition is valid, as it is within the range of acceptable values for this field.

A, C, and D are incorrect answers. A does not include 0 as an invalid partition. C does not include 0 as an invalid partition. D does not include 80 as a valid partition.

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 .

The correct answer is B, as it achieves the highest equivalence partition coverage. Equivalence partitioning is a black-box test technique that divides the input domain into partitions of equivalent data from which test cases can be derived1. In this case, the input domain is the numerical grades, and the partitions are the ranges of grades that correspond to different letter grades. Option B covers all five partitions, as it includes test inputs from each range. Option A covers only four partitions, as it does not include any test input from the range above 89. Option C covers only three partitions, as it does not include any test input from the ranges above 79 and below 60. Option D covers only two partitions, as it does not include any test input from the ranges below 79. References: 1, Section 4.2.3

The correct answer is D, as it describes exploratory testing. Exploratory testing is an experience-based test technique that involves simultaneous learning, test design, and test execution1. Exploratory testing may be used within defined time periods, during which the tester may follow a test charter as a guide. A test charter is a document that specifies the scope, objective, and approach of an exploratory testing session1. Option A is incorrect, as exploratory testing is not a suitable test technique that may replace both black-box and white-box test techniques, but a complementary technique that can be used along with other techniques1. Option B is incorrect, as exploratory testing does not require both solid specifications and much project time available for test execution, but can be used in situations where specifications are incomplete or changing and where time is limited1. Option C is incorrect, as exploratory testing is not a valid and useful black-box test technique since it focuses on test cases related to the architecture and design of a system, but an experience-based test technique that focuses on learning about the system and its behavior1. References: 1, Section 4.2.6

Statement coverage is a white-box test technique which focuses on the percentage of executable statements that has been executed by a test suite. This is the best description of statement coverage, as it measures how many statements in the source code have been covered by one or more test cases. Option A is incorrect, as it describes state transition testing, which is a black-box test technique that uses a state table to derive test cases. Option B is incorrect, as it describes error guessing, which is an experience-based test technique in which test cases are based on the tester’s knowledge of past failures. Option D is incorrect, as it describes decision coverage, which is a white-box test technique that covers the decision results which determine the next statement to be executed.

References: , Section 4.2.2

 it provides the highest level of transition coverage for the model. Transition coverage is a white-box test technique that focuses on the percentage of transitions that have been exercised by a test suite1. In this case, the model is a state transition diagram that shows the possible states and transitions of a sales order software. The diagram has five states: PLACED, IN PRODUCTION, SHIPPED, INVOICED, and CANCELLED. The diagram has nine transitions: PLACED to IN PRODUCTION, PLACED to CANCELLED, IN PRODUCTION to SHIPPED, IN PRODUCTION to CANCELLED, SHIPPED to INVOICED, SHIPPED to CANCELLED, INVOICED to CANCELLED, CANCELLED to PLACED, and CANCELLED to IN PRODUCTION. Option C covers all nine transitions in the following sequence:

• IN PRODUCTION -> SHIPPED
• SHIPPED -> INVOICED
• INVOICED -> CANCELLED
• CANCELLED -> PLACED
• PLACED -> IN PRODUCTION

Option A covers only six transitions in the following sequence:

• PLACED -> CANCELLED
• CANCELLED -> PLACED
• PLACED -> IN PRODUCTION
• IN PRODUCTION -> CANCELLED

Option B covers only five transitions in the following sequence:

• PLACED -> IN PRODUCTION
• IN PRODUCTION -> SHIPPED
• SHIPPED -> CANCELLED
• CANCELLED -> PLACED

Option D covers only four transitions in the following sequence:

• IN PRODUCTION -> CANCELLED
• CANCELLED -> PLACED
• PLACED -> IN PRODUCTION

Therefore, option C is the correct answer. Options A, B, and D are incorrect, as they do not cover all the transitions in the model. References: 1, Section 4.2.2

 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.

Test Cases 1, 2 and 3 are all valid, because they cover all the possible combinations of conditions and actions in the decision table. Test Case 1 covers the case where the employee is not a car or motorcycle driver, which leads to the action of not allowing the expense claim. Test Case 2 covers the case where the employee drives a diesel car with an engine size greater than 1600cc, which leads to the action of accepting the expense claim at band C. Test Case 3 covers the case where the employee rides a motorcycle, which leads to the action of accepting the expense claim at band A12.

The test execution schedule that meets the test plan requirements and logical dependencies is e, a, d, c, b. This schedule follows the order of re-tests first (e), followed by the highest priority tests (a and d), and then creates test data for subsequent tests (c and b). This schedule also respects the logical dependencies, as test case a creates an admin user, which is necessary for test case d to create a standard user, which is necessary for test cases c and b to perform other actions1 .