Interested to Buy Any Domain ? << Click Here >> for more details...
Differences Between Whitebox testing and Blackbox testing
- 21 Answers
- 99910 Views
- CSC, IBM, I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
Answer / rajendra
White Box Testing:Means testing the application with
coding /programming knowledge.That means the tester has to
correct the code also.
Black box testing:testing the application without
coding /programming knowledge that means the tester doesn't
require coding knowledge.Just he examines the appliaction
external fucntional beheaviour and GUI features.
byee friends
Rajendra
rajendra_penumalli@yahoo.com
| Is This Answer Correct ? | 356 Yes | 32 No |
Answer / jagadeesh
White box testing is done by the Developers. This requires
knowledge of the internal coding of the software.
Black box testing is done by the professional testing team.
This does not require knowledge of internal coding of the
application. Testing the application against the
functionality of the application with out the knowledge of
internal coding of the software.
| Is This Answer Correct ? | 220 Yes | 42 No |
Answer / jocky garg
Black box testing is done by any member of test team.because
you do not require any knowledge of coding part.in which you
have to check only its functionality and GUI
In white box testing you need good knowledge of the coding
part.it is done only by developers
| Is This Answer Correct ? | 97 Yes | 9 No |
Answer / ramana
Whitebox Testing:It is done by developers.It typically
involves in coding.In this Testing developers concentrates
on internal structure of the program and justifgies whether
that program is correct or not.
Blackbox testing: It is done by seperate Testing team. in
this testers validates the developed application by
execution of testcases and finding Bugs and send error
reports.
| Is This Answer Correct ? | 102 Yes | 26 No |
Answer / ravi garg
(1)Generally black box testing will begin early in the
software development i.e. in requirement gathering
phase itself.
But for white box testing approach one has to wait for
the designing has to complete.
2)We can use black testing strategy almost any size either
it may be small or large.
But white box testing will be effective only for small
lines of codes or piece of codes.
3)In white box testing we can not test Performance of the
application.
But in Black box testing we can do it.
4 )In general we have to write large quantity of test
cases for whitebox.
But in black box its a selcection of sample test cases.
| Is This Answer Correct ? | 91 Yes | 29 No |
Answer / amit
In blackbox testing no knowledge of code is required and
with the little knowledge of the code thats called
'greybox'testing...
Whitbox testing that is related to structual knowledge
whereas Blackbox Testing that is related to funtional
knowledge.....
| Is This Answer Correct ? | 67 Yes | 22 No |
Answer / rajeshwar rao
White box testing is nothing but coding.
It focus on the program part. Rather then finicality.
Black box testing is nothing but funcnality .
It focuses on the funcnality part rather then the program
part.
| Is This Answer Correct ? | 67 Yes | 31 No |
Answer / localp
In Black Box testing, maintainability is hard, as when the User Interface constantly change the inputs also will have to change. In White Box Testing maintainability will be much easier than Black Box test as it deals with the underline codes, and a user Interface will not affect maintainability of the program.
| Is This Answer Correct ? | 46 Yes | 14 No |
Answer / m.v.s. prasad
WHITE BOX TESTING- In this the structural part of the
application is verified.
Role- developer
BLACK BOX TESTING- In this the functional part of the
application is verified.
Role- Tester
| Is This Answer Correct ? | 5 Yes | 1 No |
Answer / karthik
Black-box: This testing methodology looks at what are the
available inputs for an application and what the expected
outputs are that should result from each input. It is not
concerned with the inner workings of the application, the
process that the application undertakes to achieve a
particular output or any other internal aspect of the
application that may be involved in the transformation of an
input into an output. Most black-box testing tools employ
either coordinate based interaction with the applications
graphical user interface (GUI) or image recognition. An
example of a black-box system would be a search engine.
You enter text that you want to search for in the search
bar, press “Search” and results are returned to you. In such
a case, you do not know or see the specific process that is
being employed to obtain your search results, you simply
see that you provide an input – a search term – and you
receive an output – your search results.
White-box: This testing methodology looks under the
covers and into the subsystem of an application. Whereas
black-box testing concerns itself exclusively with the
inputs
and outputs of an application, white-box testing enables
you to see what is happening inside the application.
Whitebox
testing provides a degree of sophistication that is not
available with black-box testing as the tester is able to
refer
to and interact with the objects that comprise an
application
rather than only having access to the user interface. An
example of a white-box system would be in-circuit testing
where someone is looking at the interconnections between
each component and verifying that each internal
connection is working properly. Another example from a
different field might be an auto-mechanic who looks at the
inner-workings of a car to ensure that all of the individual
parts are working correctly to ensure the car drives
properly.
The main difference between black-box and white-box
testing is the areas on which they choose to focus. In
simplest terms, black-box testing is focused on results. If
an action is taken and it produces the desired result then
the process that was actually used to achieve that outcome
is irrelevant. White-box testing, on the other hand, is
concerned with the details. It focuses on the internal
workings of a system and only when all avenues have
been tested and the sum of an application’s parts can be
shown to be contributing to the whole is testing complete.
| Is This Answer Correct ? | 5 Yes | 3 No |
give the format of test strategy and test methodology not the definitions i know the definition i need the template of those
What is grey box testing?
can u tell me what is orthogonal array testing?
what is the difference between BVA&ECP?
3 Answers Infinite Computer Solutions, TCS,
how much testing is enough.and why documentation is needed
1.what is meant by functional and GUI testing?
scenario is like the following, a software to be installed in the train the work of the software is when ever any object comes opposite to it the train has to be stopped would u plese any bone tell us the test case for this
what do you mean by defect,error and bug????
Beyond the customary advantages of having a testing group, what are the benefits does a company receive from a well run, automated testing group?
hi iam keeping 2+ fake exp here is my project plz tell me wt kind of Q's can be posed on it. Blue room acts as the central repository for all project information – providing detailed view into the operations of entire services of the organization. Blue room provides access to different levels of users based on their role like CEO, client, project managers, project leader and team members. Each will have permissions to access different functionality of the tool. Blue room gives access to higher management like CEO, VP or Project managers to real-time data including project completion percentages, gross margin, remaining engagement time, budget vs. actual, and profitability analysis. Through this extensive visibility, services professionals gain a better understanding of the overall performance of their services organization and are able to make faster and more effective strategic business decisions. Upload and download your Project files into Blue room from anywhere, making the latest project plans available to all participants via the Internet. n 1 more project also: Cable Network Management System (CNMS) efficiently handles customer information, billing and also effectively monitors the services provided. CNMS mainly consists of two modules. Cable Network Information (CNI) and Customer Accounts (CA). CNI maintains customer's information, employee information, service areas and tariff. CA is completely an accounting package, which helps to handle all accounting transactions of the company. The CA module is an important module and it includes account type, login information, and payment methods etc. Each customer account is linked in the system with a specific services offered to a customer, and the customer will be billed depends on his usage of these services. Customer account belongs to specific account type, which is related to some price plans and discounts. The billing process involves receiving billing records from various networks, determining the billing tariff associated with the area, calculating the bill for each customer on monthly basis, aggregating these records periodically to generate customer bills, sending bills to the customer, and collecting payments received from the customer and adjust customers balances accordingly. Up to Date Balance sheet, Import and Export feature, Network Compatible and user friendly, Rescue data through Recovery system and Dynamic Report Generation are other important features. can any 1 plz tell wt kind of test cases will be asked on dis.
Why we write test case?
what is the difference between Bug and Defect
Automation Testing 
