Black Box Testing

Black Box Testing - All programs work on some set of inputs and create some set of outputs. Black box testing looks at the program's inputs and outputs rather than the internal lines of code.

Black box testing implies that your program is literally a black box. You are not concerned with its inner workings. All you know is that when you give it a certain set of inputs, it gives back a certain set of outputs.

This is true whether the program is a report, a webpage, or an internal calculating procedure. Note that the unit testing is almost always done by the original programmer.

So, although black box testing implies that you do not know the interior workings of the program, the original developer obviously will.

This can make it more difficult to do black box testing since the original programmer may have certain biases in his or her understanding of the component that may influence how they conduct the testing.

However, even given the potential biases and assumptions, this type of testing is still fundamental to a good unit test. An example of black box testing is a webpage that takes a numeric employee ID and returns your name, address, and telephone number.

You can generate three test cases to test this requirement

  1. First, test with a valid numeric employee id.
  2. Second, test with an invalid numeric id.
  3. Then enter an employee id with alphas.

Theoretically, you could enter test cases for all valid employee ids, and you could test with an infinite number of invalid ids. However, you do not need all of them.

Three test cases for this particular example should result in proper test coverage. Another aspect of black box testing is to test at the boundaries to see if the requirement includes a valid range of input.

For instance, if a certain field can hold a number from one to a hundred, you want to test at the boundaries of the range. So, you could create five test cases of 1, 100 (the boundaries), 0, 101 (just out of bounds) and an alpha character.

Again, although there are an infinite number of test cases possible, those five should suffice.

Budget at Completion

Libro El Director de Proyectos Práctico -

Un Método probado de 28 Pasos para completar tu Proyecto Exitosamente


Por fin ─ un libro sencillo con un método paso a paso para completar tu proyecto.

¡Y sin tener conocimiento previo sobre administración de proyectos!

Toda la "paja" de la metodología de dirección de proyectos fue eliminada, dejando solo lo que es absolutamente útil para completar la tarea.

El Director de Proyectos Práctico, Project Management for Small Projects. 

Un libro pensado en el líder de proyectos empírico que salió ganador de la rifa del tigre. Pues ya tiene la responsabilidad de un proyecto, pero que no sabe ni por donde empezar. Necesita una receta ABC para seguir.

Contiene 260 páginas perfectamente detalladas con ejemplos e ilustraciones, que te llevan de la mano hasta completar tu proyecto.

Pruébalo, síguelo, ten éxito. O sigue haciendo lo mismo... :(

Disponible en Amazon

Compra aquí El Director de Proyectos Práctico en su versión electrónica─

Entrega inmediata.

BONO ADICIONAL:  El libro incluye todos los templates─plantillas─que necesitas, listos para ser usadas. No necesitas comprar nada mas.

COPYRIGHT © 2007-2012 por Hector Olvera Padilla 1853071. Reproduction in whole or in part, or translation without written permission is prohibited. "PMP®", "PMBOK®", and "PMI®" are registered marks of the Project Management Institute, Inc.