Aún no tienes acceso a esta clase

Crea una cuenta y continúa viendo este curso

Types of software testing


In this lesson you will: Understand Black-box, gray-box and white-box testing.

Challenge: using your new knowledge of Continuous Integration and testing, answer a Multiple choice quiz to reinforce your concepts.

Aportes 14

Preguntas 1

Ordenar por:

¿Quieres ver más aportes, preguntas y respuestas de la comunidad? Crea una cuenta o inicia sesión.

Some images for the concepts that we learned:

who am i? to practice is good for memory exercise thank!!

Don’t forget… Gray-box testing is mostly looking for functionality issues (not black-box 😛).

What is Continuous Integration?
Continuous Integration (CI) is a development practice where developers integrate code into a shared repository frequently, preferably several times a day. Each integration can then be verified by an automated build and automated tests. While automated testing is not strictly part of CI it is typically implied.

One of the key benefits of integrating regularly is that you can detect errors quickly and locate them more easily. As each change introduced is typically small, pinpointing the specific change that introduced a defect can be done quickly.

In recent years CI has become a best practice for software development and is guided by a set of key principles. Among them are revision control, build automation and automated testing.


Thanks Carlos, excellent class.

I like the game

White box testing is the deepest level of testing.

I did it well on the little game!! 😄

white-box testing
black-blox testing
grey-box testing

I love the game at the end.

  1. White-box testing
  2. Black-box testing
  3. Gray-box testing

**Black-Box Testing **
Done by users
No need to know the insides of the project
Testing functionality

Gray-Box Testing
Done by testers
Looking at the insides of the code
Auditing, data designed, the system added information, security

White-box Testing
Done by the developers
The deepest level of testing
Class design, duplicated code, inconsistencies, error handling, code-on-code


  1. White-box
  2. Black-box
  3. Gray-box