Académique Documents
Professionnel Documents
Culture Documents
1- What is the difference between white box, black box, and gray box testing?
Ans : Black box testing is a testing strategy based solely on requirements and specifications. Black box
testing requires no knowledge of internal paths, structures, or implementation of the software being
tested.
White box testing is a testing strategy based on internal paths, code structures, and implementation of
the software being tested. White box testing generally requires detailed programming skills.
There is one more type of testing called gray box testing. In this we look into the "box" being tested
just long enough to understand how it has been implemented. Then we close up the box and use our
knowledge to choose more effective black box tests.
2-What is Exception handling?
Ans : Exception handling is the process of responding to the occurrence, during computation, of
exceptions anomalous or exceptional events requiring special processing often changing the normal
flow of program execution. It is provided by specialized programming language constructs or computer
hardware mechanisms.
In general, an exception is handled (resolved) by saving the current state of execution in a predefined
place and switching the execution to a specific subroutine known as an exception handler. If exceptions
are continuable, the handler may later resume the execution at the original location using the saved
information. For example, a floating point divide by zero exception will typically, by default, allow the
program to be resumed, while an out of memory condition might not be resolvable transparently.
3-What is failure?
Ans : Deviation from expected result to actual result.
4-What is exploratory testing?
Ans : Exploratory testing is a hands-on approach in which testers are involved in minimum planning
and maximum test execution. The planning involves the cre-ation of a test charter, a short declaration
of the scope of a short (1 to 2 hour) time-boxed test effort, the objectives and possible approaches to
be used. The test design and test execution activities are performed in parallel typi-cally without
formally documenting the test conditions, test cases or test scripts. This does not mean that other,
more formal testing techniques will not be used. For example, the tester may decide to use boundary
value analysis but will think through and test the most important boundary values without necessarily
writing them down. Some notes will be written during the exploratory-testing session, so that a report
can be produced afterwards.
5- When is used Decision table testing?
Ans : Decision table testing is used for testing systems for which the specification takes the form of
rules or cause-effect combinations. In a decision table the inputs are listed in a column, with the
outputs in the same column but below the inputs. The remainder of the table explores combinations of
inputs to define the outputs produced.
6- What is the MAIN objective when reviewing a software deliverable?
Ans : To identify defects in any software work product.
7- Which of the following defines the expected results of a test? Test case specification or test
design specification.
Ans :Test case specification.
8-Which is the best testing model?
Ans : In real projects, tailored models are proven to be the best, because they share features from The
Waterfall, Iterative, Evolutionary models, etc., and can fit into real life time projects. Tailored models
are most productive and beneficial for many organizations. If it's a pure testing project, then the V
model is the best.