Review: test your software!

Clase 19 de 25 • Curso para Developers en Inglés (2020)

Resumen

Revisemos los conceptos aprendidos hasta el momento en las últimas clases.

Concept	Definition
Black-box Testing	It’s the kind of testing done by Users, focusing on functionality
Gray-box Testing	t’s the kind of testing done by Testers, probably looking at the data, security risks, and 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.

Lo más importante aquí es: ¡Nunca esquives las pruebas! Es muy fácil decirlo, lo sé. En la teoría, como desarrolladores o desarrolladoras de software, nos corresponde invertir un 20% de nuestro tiempo de desarrollo de pruebas. Habla con tu equipo y transmite la importante de generarlas de forma automatizada, esto les ahorrará varios dolores de cabeza.

Contribución creada por Kevin Fiorentino con aportes de Erwin Alan Frías Martínez.

Erwin Frias

student•

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.

DANIEL ALBERTO PRADA HERRERA

student•

Never skip Summaries! jajaja, Thanks again

Felipe Bernardo González Barranco

student•

Jajaja, keep doing it!

Cristian Blandón

student•

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):

Continuously submitting working, runnable software into source control.
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).

Sandra Milena Rojas Herrán

student•

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-

Carlos Arriaga

teacher•

No problems Sandra. It IS a lengthy course, but it is also very complete. I loved creating it!!!!!

Carlos Eduardo Magallon Zepeda

student•

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

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.

Francisco Velasco

student•

Never say never! je

Felipe Bernardo González Barranco

student•

-Justin Bieber.

Daniel Elías Ángel Barreto

student•

Libro clean code

Ena Michelle Lovos Ortiz

student•

Awesome

Ena Michelle Lovos Ortiz

student•

Also

Ena Michelle Lovos Ortiz

student•

Firts

Ena Michelle Lovos Ortiz

student•

😀😀

Ena Michelle Lovos Ortiz

student•

Thanks

Krissia Julissa Campos Cruz

student•

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-

Krissia Julissa Campos Cruz

student•

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.

Emeli Yorleny Recinos Mojica

student•

Thanks

Johana Saraí Isleño Ayala

student•

excellent

Litzy Jasvell Martínez Calero

student•

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).

Litzy Jasvell Martínez Calero

student•

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 focuse

Litzy Jasvell Martínez Calero

student•

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 th

Litzy Jasvell Martínez Calero

student•

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

Continuously submitting

Litzy Jasvell Martínez Calero

student•

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 t