ISTQB Foundation Level Exam Crash Course Part-32
This is the Part 32 of 35 containing 5 Questions (Q. 156 to 160) with detailed explanation as expected in ISTQB Foundation Level Exam Latest Syllabus updated in 2011
Deep study of these 175 questions shall be of great help in getting success in ISTQB Foundation Level Exam
Q. 156: Describe various potential risks associated with the usage of test supporting tools.
1) Unrealistic expectations of the tool performance which may include the functionality & ease of use.
2) Underestimated time, cost & effort to introduce & train the users in using the tool.
3) Underestimated time & effort needed to gain significant benefits from the tool usage.
4) Underestimated effort required in maintaining the test resources or assets produced by the tool.
5) Over dependence on the tool
<<<<<< =================== >>>>>>
Q. 157: What are the various sections that form the part of a typical test summary report as per IEEE standard for Software test documentation?
Test summary report generally includes following sections.
a) Test summary report Identifier;
b) Summary;
c) Variances;
d) Comprehensive assessment;
e) Results summary;
f) Evaluation;
g) Activities or events summary;
h) Approvals;
<<<<<< =================== >>>>>>
Q. 158: What are the activities involved in each of the main phases in a formal review.
Phase-1: Planning phase:
a) Selection of personnel
b) Allocation of roles
c) Definition of entry & exit criteria
d) Selection of the parts of the documents that need to be referred.
Phase-2: Kick off phase:
a) Distribution of documents
b) Explanation of objectives, process & documents to various participants.
c) Checking of the entry criteria
Phase-3: Individual preparation phase:
a) Noting of potential defects
b) Noting of questions & comments.
Phase-4: Review meeting phase:
a) Logging of defects
b) Submission of recommendations for handling defects
c) Making decisions about defects
Phase-5: Reworking phase:
a) Fixing of defects
Phase-6: Following up phase:
a) Checking that defects have been addressed or resolved
b) Gathering metrics
c) Checking or verification on the exit criteria.
<<<<<< =================== >>>>>>
Q. 159: What are the points of difference between black-box testing & white-box testing?
Black-box testing is a testing technique in which the internal structure of the component or system being tested is not known to the tester. These tests can be functional or can be non functional & these are applicable to all levels of software testing; may it be unit or component testing, integration testing, functional testing, system testing or even acceptance testing. While black-box testing can uncover unimplemented parts of the specification, it does not guarantee that all existent parts are tested.
White-box testing is a testing technique in which the tester is allowed to look inside the box. It focuses specially on using the internal structure of the component or the system being tested. Tests generated based upon this technique incorporate coverage of the written code, branches, paths, statements & the internal logic of the code.
<<<<<< =================== >>>>>>
Q. 160: What are the points of differentiation between component testing & integration testing?
Component testing is the process of finding out defects in the software units, plus verification of functions of different software units. The software units can be modules, programs, objects, classes etc. in individual capacity. Component testing is generally done by the programmers.
Integration testing is the process of testing the interface between the components. This involves testing of components combined as a group to verify if an individual component is interacting with others correctly or not. Integration testing is done by the programmers or testers.
Part – 33 of the Crash Course – ISTQB Foundation Exam
An expert on R&D, Online Training and Publishing. He is M.Tech. (Honours) and is a part of the STG team since inception.