| Topic :: |
Black Box Testing |
|
Topic Submitted By :: Swapna |
| |
Reply Posted By |
| |
|
Re: Black Box Testing |
Reply # 1 |
Testing software without any knowledge of the inner
workings, structure or language of the module being tested.
Black box tests, as most other kinds of tests, must be
written from a definitive source document, such as a
specification or requirements document.
 |
Anirudhjain |
| |
|
Re: Black Box Testing |
Reply # 2 |
Testing the application without any knowledge of Internal
design.  |
Jayamurugan.s |
| |
|
|
| |
| |
|
Re: Black Box Testing |
Reply # 3 |
Testing the given application without knowing internal code
and logic.  |
Rajendraprasad |
| |
|
Re: Black Box Testing |
Reply # 4 |
Hi,
Black box testing is the testing in which we do not have any
knoweledge of the internel code,we work with the valid input
and expected output.A good ex for Black Box Testing is :We
drive the car,we know how to drive the car but we dont know
about the internal structure.
Plz correct me if i m wrong..
nitin9360@gmail.com  |
Nitin Verma |
| |
|
Re: Black Box Testing |
Reply # 5 |
Testing the application without specific knowledge on plat
form and without Internal logic.  |
Ravinder |
| |
|
Re: Black Box Testing |
Reply # 6 |
Testing the functionality of the application without having
internal structural knowledge(Coding).  |
Pswapnasri |
| |
|
Re: Black Box Testing |
Reply # 7 |
Hi,
I agree with you all blackbox testing means conducts the
testing without knowledge on the internal structure.But
mainly we can use the two techniques when we conduct the
black box testing:1) Boundary value analysis (BVA)
2) Equivalance particion (EQP)
and remaining are Error guessing and all.
 |
Venkatsrqa |
| |
|
Re: Black Box Testing |
Reply # 8 |
It is a build level testing technique where the test
engineers concentrate external interface validate to
internal processing or meet customers requirements in terms
of functionality  |
Siba Prasad Mishra |
| |
|
Re: Black Box Testing |
Reply # 9 |
Black Box Testing is testing without knowledge of the
internal workings of the item being tested.
For example, when black box testing is applied to software
engineering, the tester would only know
the "legal" inputs and what the expected outputs should be,
but not how the program actually arrives
at those outputs. It is because of this that black box
testing can be considered testing with respect
to the specifications, no other knowledge of the program is
necessary
dvantages of Black Box Testing
* more effective on larger units of code than glass box
testing
* tester needs no knowledge of implementation, including
specific programming languages
* tester and programmer are independent of each other
* tests are done from a user's point of view
* will help to expose any ambiguities or inconsistencies
in the specifications
* test cases can be designed as soon as the
specifications are complete
Disadvantages of Black Box Testing
* only a small number of possible inputs can actually be
tested, to test every possible input stream would take
nearly forever
* without clear and concise specifications, test cases
are hard to design
* there may be unnecessary repetition of test inputs if
the tester is not informed of test cases the programmer has
already tried
* may leave many program paths untested
* cannot be directed toward specific segments of code
which may be very complex (and therefore more error prone)
* most testing related research has been directed toward
glass box testing
 |
Shilpa Saraf |
| |
| |
| |
| |
| |