Answer Posted / 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.

How to write test cases for nevigating menus? Ex. Course -Topics -Subtopics

2143

---

What is mutation testing & when can it be done?

1103

---

PLEASE CAN ANYONE SEND ME THE TEST SCENARIO BASED QUESTIONS FOR 3+ EXPERIENCE IN MANUAL TESTING

4286

---

what is test scenario and test condition?

1977

---

online demo for bug tracker tool(let me know the website)

2075

---

Can you explain steps in function points?

1047

---

Can any1 tell me suppose u r doing manual testing on unix platform with Shell Script, then how it is done? How u r implementing it & what is the use of Shell scripting on Manual Testing? plzzzzzzz i need ur help.

2207

---

i need manual testing interview questions for 2+ experience plzz help me..

4472

---

1.Enlist the types of testing performed for any window in sequence? 2.Use of edit_get_list function 3.Accuracy & Precision

2100

---

hi experts, i was asked to write down the requirement description,test scenario, and test cases for gmail login and send email and then to check the email was sent in the sent mails.the format given to me was like this: Req ID, Req description, Test Scenario, Test cases....Can anybody please help me out with this..

1992

---

What is test startegy?

1184

---

What is test out put?

2067

---

What are some best practices that you should follow when writing test cases?

1162

---

Describe to me what you see as a process. Not a particular process, just the basics of having a process.

2137

---

what is diffrence between dynamic black box testing and dynamic white box testing

1953

---