Aún no tienes acceso a esta clase

Crea una cuenta y continúa viendo este curso

Review: test your software!

20/27
Recursos

In this lesson you will read and remember the concepts we have studied so far.

Challenge: read the concepts and definition of what we have covered so far to reinforce your knowledge.

Aportes 7

Preguntas 0

Ordenar por:

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

Black-box Testing It’s the kind of testing done by Users, focusing on functionality.
Gray-box Testing It’s the kind of testing done by Testers, probably looking at the data, security risks, auditing.
White-box Testing Deep testing done by other developers, looking for inconsistencies in the Code.
Continuous Integration (CI) Continuous Integration is a technique that guarantees the reduction in the impact of conflicts.
Test-Driven Development (TDD) TDD is all about writing tests before you start writing the code that will give the software its functionality, and will allow you to have solid, specific ideas about what your Software needs to do.
Make your code go from RED to GREEN The only goal you should have at this point is to get your tests to pass. That is to go “GREEN”.
Never Skip Tests! People aren’t great at performing repetitive tasks carefully, but computers are. Always test your Code.

I share with you some of my notes 😃

CONTINUOUS INTEGRATION

A technique that guarantees the reduction in the impact of conflicts while developing software (avoiding merge hell, ensuring ownership and fixing bugs quickly):

  1. Continuously submitting working, runnable software into source control.
  2. Using automation to enable source control to build and test the latest versions of the code.

TESTING

  • TDD (Test-driven-development): all about designing tests first, then code based on those tests. Testing is the driver, the motivator, where all start, making the code go from Red to Green. Every module is designed to pass a test.
  • Black-box testing: performed by users, seeing the system from outside, just functionality. No code, database, algorithm, input or output evaluations.
  • Gray-box testing: performed by testers, opening the hood of the software to look for more specific things, but also focused on functionality (security risks, memory leaks, uninstallation).
  • White-box testing: deepest level of testing performed by other developers (class designs, duplicated code, inconsistencies, error handling (will try to break up the code).

Understanding Continuous Integration (CI) and testing

Black-box

Done by users. Only looks for functionality. Users can test the software from the outside, no database, code, nor algorithm evaluation.

gray-box

Done by testers. The aspects to test are code, database evaluation, security risk, memory leaks.

white-box

Executed by developers. The deepest level of testing.

  • Class designs
  • Duplicate code
  • Branches
  • Error handling
  • Code on code

Handle accidents when building the code

CI

Guarantees the reduction in the impact of conflicts by:

  • Continuously submitting working code
  • Use automation software to control changes.
  • Source control emails developers involved in the last change
  • CI wraps version control, compilation and testing into a single repetable process

TTD Test-driven development

Design and write tests first then write code. It’s all about moving your code from red to green. Tests are a must, never skip them.

Thanks teacher. Although, I think that I have take much time in this course, It has been the best, because until the moment, I am going well. I have enjoyed this course, seriously. Thanks-

Never say never! je

Notes:

  • Black-box Testing: It’s the kind of testing done by Users, focusing on functionality.

  • Gray-box Testing: It’s the kind of testing done by Testers, probably looking at the data, security risks, auditing.

  • White-box Testing: Deep testing done by other developers, looking for inconsistencies in the Code.

  • Continuous Integration (CI): Continuous Integration is a technique that guarantees the reduction in the impact of conflicts.

  • Test-Driven Development (TDD): TDD is all about writing tests before you start writing the code that will give the software its functionality, and will allow you to have solid, specific ideas about what your Software needs to do.

  • Make your code go from RED to GREEN: The only goal you should have at this point is to get your tests to pass. That is to go “GREEN”.

  • Never Skip Tests! People aren’t great at performing repetitive tasks carefully, but computers are. Always test your Code.