<p>I will make my answer, based on the knowledge for security testing, but IMHO this can be generalized.</p>

<ul>
<li><p>Black box testing - when the tester know nothing about the system, components, liaisons, connections, etc. This can be helpful more like UI/UX testing, functional testing. Example: you do not work for Microsoft and also you do not have the source code and need to test MS Office</p></li>
<li><p>Gray box testing - when the tester have some knowledge about how the system work, some information about internals.</p></li>
<li><p>White box testing - when the tester have or can get all the information about internals, connections, principles of work of the tested product. Example: testing Linux kernel.</p></li>
</ul>

<p>For reference:</p>

<p><a href="https://en.wikipedia.org/wiki/Black-box_testing" rel="noreferrer">Black box testing</a> (Wikipedia)</p>

<p><a href="https://en.wikipedia.org/wiki/White-box_testing" rel="noreferrer">White box testing</a> (Wikipedia)</p>

<p><a href="https://en.wikipedia.org/wiki/Gray_box_testing" rel="noreferrer">Gray box testing</a> (Wikipedia)</p>

CC BY-SA 3.0
2017-02-28T19:35:42.397Z
2017-02-28T19:42:05.033Z
2017-02-28T19:42:05.033Z
Romeo Ninov
<p>As answered by <a href="https://devops.stackexchange.com/users/57/romeo-ninov">Romeo Ninov</a> in Black Box testing, tester is unaware about the application internal structure.</p>

<blockquote>
  <p>This method is named so because the software program, in the eyes of
  the tester, is like a black box; inside which one cannot see. This
  method attempts to find errors in the following categories:</p>
  
  <ul>
  <li>Incorrect or missing functions</li>
  <li>Interface errors</li>
  <li>Errors in data structures or external database access</li>
  <li>Behavior or performance errors</li>
  <li>Initialization and termination errors</li>
  </ul>
</blockquote>

<p>Refrence:</p>

<ul>
<li><a href="http://softwaretestingfundamentals.com/black-box-testing/" rel="nofollow noreferrer">http://softwaretestingfundamentals.com/black-box-testing/</a></li>
</ul>

CC BY-SA 3.0
2017-03-01T07:25:46.197Z
2017-03-01T07:25:46.197Z
2017-04-13T13:01:29.297Z
Abhishek Gurjar
<p>What is "black box" testing and how it is different from ordinary testing? For example black box tests prior to deploying to production.</p>

<p><strong>Note</strong>: "black box" testing is a common requirement when applying for devops roles (not necessary a tester thing).</p>

CC BY-SA 3.0
2017-03-01T09:13:06.773Z
I'm voting to close this question as off-topic because it belongs to the this question belongs in the Software Quality Assurance & Testing SE, not here
Rsf
CC BY-SA 3.0
2017-03-01T11:06:43.133Z
@Rsf or to http://security.stackexchange.com/ [White-box vs. Black-box](http://security.stackexchange.com/questions/214/white-box-vs-black-box)
Tensibai
CC BY-SA 3.0
2017-03-01T11:19:34.110Z
Voting to close this, as it is better suited for other SE sites.
Evgeny Zislis
CC BY-SA 3.0
2017-03-01T11:22:56.857Z
Yes, it can fall under different categories. I think the best approach would be  to send general SQA questions to SQA, and questions where domain knowledge is needed to the relevant SE.
Rsf
<terminology><testing><dtap>
What is "black box" testing?
kenorb
# What is "black box" testing?

(Asked by: username_0 on 2017-02-28)

What is "black box" testing and how it is different from ordinary testing? For example black box tests prior to deploying to production.

**Note**: "black box" testing is a common requirement when applying for devops roles (not necessary a tester thing).

**Tags:** terminology, testing, dtap

> **Comments:**
> **username_1**: I'm voting to close this question as off-topic because it belongs to the this question belongs in the Software Quality Assurance & Testing SE, not here  
> **username_2**: @username_1 or to http://security.stackexchange.com/ [White-box vs. Black-box](http://security.stackexchange.com/questions/214/white-box-vs-black-box)  
> **username_3**: Voting to close this, as it is better suited for other SE sites.  
> **username_1**: Yes, it can fall under different categories. I think the best approach would be  to send general SQA questions to SQA, and questions where domain knowledge is needed to the relevant SE.  

---

## 2 answers

### Answer by username_4 on 2017-02-28. Score: 6 | Accepted answer

I will make my answer, based on the knowledge for security testing, but IMHO this can be generalized.

* Black box testing - when the tester know nothing about the system, components, liaisons, connections, etc. This can be helpful more like UI/UX testing, functional testing. Example: you do not work for Microsoft and also you do not have the source code and need to test MS Office
* Gray box testing - when the tester have some knowledge about how the system work, some information about internals.
* White box testing - when the tester have or can get all the information about internals, connections, principles of work of the tested product. Example: testing Linux kernel.

For reference:

[Black box testing](https://en.wikipedia.org/wiki/Black-box_testing) (Wikipedia)

[White box testing](https://en.wikipedia.org/wiki/White-box_testing) (Wikipedia)

[Gray box testing](https://en.wikipedia.org/wiki/Gray_box_testing) (Wikipedia)


---

### Answer by username_5 on 2017-03-01. Score: 2

As answered by [username_4](https://devops.stackexchange.com/users/57/romeo-ninov) in Black Box testing, tester is unaware about the application internal structure.

> This method is named so because the software program, in the eyes of
> the tester, is like a black box; inside which one cannot see. This
> method attempts to find errors in the following categories:
>
> * Incorrect or missing functions
> * Interface errors
> * Errors in data structures or external database access
> * Behavior or performance errors
> * Initialization and termination errors

Refrence:

* <http://softwaretestingfundamentals.com/black-box-testing/>


---

