iSQI CTFL2018 CTFL_Syll2018 New Questions

The statement that use case testing is designed to find defects in the process flow is true, because use case testing is a technique that tests the end-to-end user interactions and outcomes based on use cases or scenarios that describe how the software under test should be used . Use case testing can help to find defects in the process flow, such as missing steps, incorrect sequences, or invalid transitions . The other options are not true statements about use case testing. Option A is false, because use case testing is not designed to be used by real users, but rather by professional testers who design and execute test cases based on use cases or scenarios . Option C is false, because use case testing is not designed to find defects in the data flow, but rather in the process flow. Data flow testing is a different technique that tests how data values are defined, used, and modified by the software under test . Option D is false, because use case testing is not always designed by customers or end users, but rather by testers who analyse the requirements or specifications of the software under test to identify use cases or scenarios .

The order in which the specifications for test cases, test conditions and test procedures are developed as a part of the test development process is as follows:

• Test Condition: A test condition is an item or event of a component or system that could be verified by one or more test cases, such as a function, transaction, feature, quality attribute, or structural element.
• Test Case: A test case is a set of input values, execution preconditions, expected results and execution postconditions, developed for a particular objective or test condition, such as to exercise a particular program path or to verify compliance with a specific requirement.
• Test Procedure: A test procedure is a document providing detailed instructions for the execution of one or more test cases.

Therefore, the correct order is test condition --> test case --> test procedure.

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

Multiple condition coverage is a structure-based test technique that aims to achieve a high level of coverage by testing all possible combinations of conditions and outcomes in each decision point of the code or design of the system under test. Multiple condition coverage verifies that each condition in a decision point has an effect on the outcome and that there are no hidden defects or logical errors in the code or design. Multiple condition coverage requires some knowledge of the internal structure or implementation of the system under test; it focuses on how the system does what it does rather than what it does. Multiple condition coverage is one of the most rigorous and complex structure-based test techniques because it can generate a large number of test cases for each decision point, especially if there are many conditions involved. You can find more information about multiple condition coverage in [A Study Guide to the ISTQB® Foundation Level 2018 Syllabus], Chapter 4, Section 4.3.

A configuration management tool is a tool that allows users to manage and control the versions and changes of software artifacts, such as code, documents, test cases, etc. A configuration management tool can help prevent the loss of Sam’s updates by:

• Providing a centralized repository where Sam can store and retrieve his test cases and other artifacts
• Keeping track of the history and status of each artifact and allowing Sam to compare and revert to previous versions if needed
• Supporting collaboration and communication among team members by allowing them to share and access the latest versions of the artifacts

The other tools mentioned in the question are not relevant for this scenario because they do not provide the same functionality or benefits as a configuration management tool. For example:

• A. Incident management tool: This tool type allows users to record, track, manage, and report the defects found during testing. It does not help with managing or controlling the versions or changes of test cases or other artifacts.
• C. Test execution tool: This tool type allows users to execute test cases automatically or semi-automatically and compare the actual results with the expected results. It does not help with managing or controlling the versions or changes of test cases or other artifacts.
• D. Backup tool: This tool type allows users to create copies of data or files and store them in a different location or device for recovery purposes. It does not help with managing or controlling the versions or changes of test cases or other artifacts.

You can find more information about configuration management tools in [A Study Guide to the ISTQB® Foundation Level 2018 Syllabus], Chapter 6, Section 6.4.