ExamGecko
Home / ISTQB / CTFL-2018
Ask Question

ISTQB CTFL-2018 Practice Test - Questions Answers, Page 27

Question list
Search

Question 261

Report
Export
Collapse

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

Test Procedure --> Test Condition -> Test Case
Test Procedure --> Test Condition -> Test Case
Test Condition --> Test Case --> Test Procedure
Test Condition --> Test Case --> Test Procedure
Test Procedure -> Test Case -> Test Condition
Test Procedure -> Test Case -> Test Condition
Test Condition --> Test Procedure --> Test Case
Test Condition --> Test Procedure --> Test Case
Suggested answer: B

Explanation:

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.

asked 18/09/2024
Chris Bezuidenhout
39 questions

Question 262

Report
Export
Collapse

When should component integration tests be carried out?

Integration tests should always be done after system tests
Integration tests should always be done after system tests
Integration tests should be done at the customer's site, after acceptance tests
Integration tests should be done at the customer's site, after acceptance tests
Integration tests can be done before or after system tests
Integration tests can be done before or after system tests
Integration tests should always be done before system tests
Integration tests should always be done before system tests
Suggested answer: D

Explanation:

Component integration testing is the process of testing the interactions between different components of a system. It should always be done before system testing, which is the process of testing the system as a whole. Integration testing can reveal defects in the interfaces and interactions between components, which can affect the functionality and performance of the system. System testing can reveal defects in the system requirements, design, and behavior, which can affect the quality and usability of the system. Therefore, it is logical to perform integration testing before system testing, to ensure that the components work together correctly before testing the system as a whole.

asked 18/09/2024
Ivan Pavlek
36 questions

Question 263

Report
Export
Collapse

Which of the following activities do NOT belong to test implementation and execution?

Checking if the preconditions of test execution have been met
Checking if the preconditions of test execution have been met
Logging of test results
Logging of test results
Test data generation
Test data generation
Prioritizing test conditions
Prioritizing test conditions
Suggested answer: D

Explanation:

Test implementation and execution is the phase of the test process where test cases are executed and test results are logged. It includes activities such as checking if the preconditions of test execution have been met, executing test cases according to a test procedure, comparing actual results with expected results, logging test results and reporting defects, and repeating test activities as needed. Prioritizing test conditions is not an activity that belongs to test implementation and execution, but rather to test analysis and design, which is the phase where test conditions are identified and test cases are designed.

Reference:Certified Tester Foundation Level Syllabus, Section 4.2.3 and 4.2.4

asked 18/09/2024
Mark Theeuwes
41 questions

Question 264

Report
Export
Collapse

Choose below the best characterization of the difference between black-box testing and white-box testing

For black-box testing, the testers do not need to know the test object in advance
For black-box testing, the testers do not need to know the test object in advance
For white-box testing, the testers have to consult specifications and developers before running any tests
For white-box testing, the testers have to consult specifications and developers before running any tests
Black box testing uses static analysis. White box testing uses dynamic analysis
Black box testing uses static analysis. White box testing uses dynamic analysis
Black-box testing is based on the test basis documentation. White-box testing is based on an analysis of the code itself.
Black-box testing is based on the test basis documentation. White-box testing is based on an analysis of the code itself.
Black-box testing is based on an analysis of the code itself White-box testing is based on the test basis.
Black-box testing is based on an analysis of the code itself White-box testing is based on the test basis.
Suggested answer: D

Explanation:

Black-box testing and white-box testing are two approaches to test design that differ in the way they derive test cases from the test basis. Black-box testing is based on an analysis of the test basis documentation, such as requirements, specifications, user stories, or use cases, without looking at the internal structure or code of the system under test. White-box testing is based on an analysis of the code itself, such as statements, branches, paths, or data flows, to design test cases that cover specific aspects of the code. Black-box testing focuses on the external behavior and functionality of the system, while white-box testing focuses on the internal logic and structure of the system.

asked 18/09/2024
Jermaine Wells
41 questions

Question 265

Report
Export
Collapse

For a mandatory input field 'ZIP code' the following rules are given:

1 - The valid ZIP code format is 5 numeric digits

2 - The code has to exist in the pest office's official ZIP code list

Using equivalence classes partitioning, how many test cases are required to test this field?

6
6
4
4
8
8
3
3
Suggested answer: B

Explanation:

Equivalence partitioning is a technique to divide a set of possible inputs or outputs into classes that are expected to behave similarly or produce similar results. For each equivalence class, only one test case is required to represent the whole class. In this case, we can identify the following equivalence classes for the input field 'ZIP code':

Valid ZIP code format and valid ZIP code value (e.g., 12345)

Valid ZIP code format and invalid ZIP code value (e.g., 99999)

Invalid ZIP code format and valid ZIP code value (e.g., 1234)

Invalid ZIP code format and invalid ZIP code value (e.g., ABCDE)

Therefore, four test cases are required to test this field using equivalence partitioning.

asked 18/09/2024
Vicky Mukhy
31 questions

Question 266

Report
Export
Collapse

Which of the following statements about independent testing is WRONG?

Independent testing is necessary because developers don't know any testing
Independent testing is necessary because developers don't know any testing
A certain degree of independence makes the tester more effective at finding defects
A certain degree of independence makes the tester more effective at finding defects
Independent testing is best suited for the system test level
Independent testing is best suited for the system test level
Independent test teams may find other types of defects than developers who are familiar with the system's structure.
Independent test teams may find other types of defects than developers who are familiar with the system's structure.
Suggested answer: A

Explanation:

The statement that independent testing is necessary because developers don't know any testing is wrong. Developers do know some testing, as they perform unit testing and component testing on their own code. However, independent testing is beneficial because it can provide a different perspective and a higher degree of objectivity than testing done by developers. Independent testers may have different skills, knowledge, experience, and expectations than developers, which can help them find different types of defects and improve the quality of the system.

asked 18/09/2024
Arkadius Thoma
49 questions

Question 267

Report
Export
Collapse

Integration testing has following characteristics.

I, It can be done in incremental manner

II, It is always done after system testing

II,I, It includes functional tests

IV It includes non-functional tests

I, l and IV are correct
I, l and IV are correct
I Ill and IV are correct
I Ill and IV are correct
TI is correct
TI is correct
II, and II,I are correct
II, and II,I are correct
Suggested answer: B

Explanation:

Integration testing is the process of testing the interactions between different components or subsystems of a system. It has the following characteristics:

It can be done in an incremental manner, meaning that components or subsystems are integrated and tested one by one until the whole system is integrated and tested.

It is usually done before system testing, which is the process of testing the system as a whole against its requirements and specifications.

It includes functional tests, which are tests that verify the functionality and behavior of the system or its components.

It includes non-functional tests, which are tests that verify the quality attributes of the system or its components, such as performance, reliability, security, etc.

Therefore, statements I, II,I, and IV are correct.

asked 18/09/2024
Rajiv Ranjan
52 questions

Question 268

Report
Export
Collapse

Which of the following is NOT a common objective of testing?

Providing information on the status of the system
Providing information on the status of the system
Preventing defects
Preventing defects
Finding defects in the software
Finding defects in the software
Debugging the software to find the reason for defects
Debugging the software to find the reason for defects
Suggested answer: D

Explanation:

Debugging the software to find the reason for defects is not a common objective of testing. Debugging is the process of finding, analyzing, and removing the causes of failures in software. Debugging is usually done by developers after testers have reported defects found during testing. Testing is the process of evaluating software by applying test cases to find defects and provide information on its quality. Testing has several common objectives, such as:

Providing information on the status of the system, such as its readiness for release, its compliance with requirements, its risks and issues, etc.

Preventing defects, by applying good practices throughout the software development lifecycle, such as reviews, inspections, static analysis, etc.

Finding defects in the software, by applying test cases that cover different aspects of the software functionality, quality, performance, security, etc.

Therefore, statement D is not correct.

asked 18/09/2024
MD Farmudin Safi
37 questions

Question 269

Report
Export
Collapse

Which of the following DOES NOT describe 'component testing'?

Component testing tests interfaces between modules and interactions of different parts of a system.
Component testing tests interfaces between modules and interactions of different parts of a system.
Component testing occurs with access to the code being tested and with the support of a development environment, such as a unit test framework or debugging tool
Component testing occurs with access to the code being tested and with the support of a development environment, such as a unit test framework or debugging tool
Component testing verifies the functioning of. software modules, programs, objects, classes, etc. that are separately testable.
Component testing verifies the functioning of. software modules, programs, objects, classes, etc. that are separately testable.
In component testing stubs, drivers and simulators may be usefully utilized to facilitate tester activity
In component testing stubs, drivers and simulators may be usefully utilized to facilitate tester activity
Suggested answer: A

Explanation:

The statement that component testing tests interfaces between modules and interactions of different parts of a system does not describe component testing. Component testing is the process of testing individual software components that are separately testable, such as modules, programs, objects, classes, etc. Component testing verifies the functionality and quality of the components in isolation from other components. Component testing does not test the interfaces or interactions between components, as this is done in integration testing.

asked 18/09/2024
Steve Marechal
37 questions

Question 270

Report
Export
Collapse

Which type of software development product can undergo static testing?

Any software development product can undergo static testing, including requirements specifications, design specifications and code
Any software development product can undergo static testing, including requirements specifications, design specifications and code
Static testing is done only on the requirements. You need to execute the software in order to find defects in the code
Static testing is done only on the requirements. You need to execute the software in order to find defects in the code
Static testing is done only on the code as part of the 'code review' sessions Other documents are reviewed, but not by static testing Static tests
Static testing is done only on the code as part of the 'code review' sessions Other documents are reviewed, but not by static testing Static tests
should be performed on the installation and user guide documents as these documents are used by the end user
should be performed on the installation and user guide documents as these documents are used by the end user
Suggested answer: A

Explanation:

Any software development product can undergo static testing, including requirements specifications, design specifications, code, test cases, test plans, user manuals, etc. Static testing is a type of testing that does not involve executing the software or system under test, but rather analyzing it using various techniques, such as reviews, inspections, walkthroughs, checklists, static analysis tools, etc. Static testing can help find defects and improve the quality of any software development product at any stage of the software development lifecycle.

asked 18/09/2024
Akshi Raj
42 questions
Total 365 questions
Go to page: of 37