No tienes acceso a esta clase

隆Contin煤a aprendiendo! 脷nete y comienza a potenciar tu carrera

Adquiere por un a帽o todos los cursos, escuelas y certificados por un precio especial.

Antes: $249

Currency
$219/a帽o

Paga en 4 cuotas sin intereses

Paga en 4 cuotas sin intereses
Comprar ahora

Termina en:

1D
4H
17M
24S

Functional and unit testing

14/25
Recursos

Las pruebas de tu software son clave para tener confianza en su funcionamiento y asegurar calidad del mismo.

Pruebas funcionales

Como desarrollador de software, tambi茅n eres responsable de las pruebas de tu aplicaci贸n. M谩s all谩 de tener un equipo que se encargue de eso, t煤 puedes aportar mucho con tus propias pruebas.

  • What things can go wrong in a development project?
  • Different problems will arise when working.
  • Sometimes even the best developer breaks the build.
  • There are a lot of good frameworks out there. It is a collection of tools that help you build tour tests.
  • Your tests need to guarantee your software鈥檚 optimal functionality. Always think about functional testing.
  • Remember, they only run your tests, they don鈥檛 build them for you.

T茅cnica #3 - Pruebas unitarias

Existen varios tipos de pruebas que tu mismo puedes implementar junto con tu equipo de trabajo.

  • Manual testing: A developer or group of developers that manually start testing the code鈥檚 functionality.
  • Automated testing: If you have a more complex piece of software, then it will be much better to perform automated testing.

Testing unitario

  • It is all about creating automatic tests for the smallest components of the code to test their business logic. That is going to be essential to the development and the effectiveness of your testing.
  • Unite testing ties in together with the continuous integration process many companies have, whenever new code is submitted to source control the software will test the build and email people to let them know there is a problem with their code.

Pruebas unitarias frente a pruebas del sistema

  • Things may work great in isolation, but when different components of the code interact or when users use the system, bugs can be overlooked.
  • System testing, hooking everything together and then treating it like a black box. It focuses on the overall functionality, making sure the system handles interactions well.

T茅cnica #4 - Deje que sus compa帽eros entiendan su c贸digo - 隆Docum茅ntelo!

Documentar tu c贸digo puede ser una tarea odiosa, pero extremadamente importante para tus compa帽eros de trabajo y para el futuro del proyecto.

  • Have stand-up meetings to:
    • Inform your customers of any changes you have made to the code.
    • Document your changes.
    • Analyze them along with your peers.
    • Keep them informed of reasons.
  • It鈥檚 important you become an expert communicator, and standup meetings will be the place where you will require to shine.
  • Find ways to adapt your speech depending on your listeners.

Documenta tu c贸digo

  • Most problems in Software Development are related to Communication.
  • Any changes or tests you perform on your Code should be documented, especially when working with Version Control.
  • Remember to write good commit messages, especially when using Version Control, these messages should be descriptive so other developers can understand your changes.
  • You can also 鈥渢ag鈥 your code. A 鈥渢ag鈥 is a snapshot of your code at a certain time.
  • You can use tags to keep track of major progress in your software, like milestones, iterations, or changes in requirements.
  • Many issues can be solved by communicating effectively with your peers.

Escribir pruebas para tu c贸digo es la mejor documentaci贸n que puedes hacer. Sin embargo, no esquives la responsabilidad de comunicar y compartir el proyecto. Un consejo personal: documenta tu c贸digo en una tarde tranquila de trabajo, esucha m煤sica y anota las palabras que describen qu茅 fue lo que hiciste y c贸mo funciona. Busca la manera de divertirte mientras lo haces.


Contribuci贸n creada por: Kevin Fiorentino.

Aportes 17

Preguntas 0

Ordenar por:

驴Quieres ver m谩s aportes, preguntas y respuestas de la comunidad?

o inicia sesi贸n.

Debriefing is the action of letting other people or informing other people of the changes or just basically telling them if you have done something extra. You have done something differently.

From my experience I would say that communication with our peers is a fundamental pillar to have a good workflow.

Functional testing
Come up with tests
It needs to guarantee your software鈥檚 optimal functionality

Technique 3: Unit Testing
Test the smallest pieces of code, it ties with continuous integration process

Manual testing: A group of developers manually starts testing the code鈥檚 functionality

Automated testing: For a more complex piece of software

System testing: Test things together, as a black box testing. Tests the overall functionality

Technique 4: Document it
Debriefing: Let your peers understand your code.
Become an expert communicator, know who is listening to you

Functional testing:

  • What things can go wrong in a development project?
  • Coming up with tests is your job.
  • You need to guarantee your software鈥檚 optimal functionality.
    Technique #3 - ALways exercise your code-unit testing.
  • Manual testing: Developers manually start testing the code鈥檚 functionality.
  • Automated testing: If your software is more complex, it will be much better to perform automated testing.
  • Unit testing: Creating automated tests for the smallest components of the code to test their business logic.
    Technique #4 - Let your peers understand your code-document it!
    Debriefing - Let your peers understand your code - Document it.
    Have to stand up meetings to:
  • Inform your customers of any changes you have made to the code.
  • Document your changes.
  • Analyze them along with your peers.
  • Keep them informed reasons.
  • It鈥檚 important you become an expert communicator.

This course is great, I鈥檇 like to get more English courses for Developers, like workshops for instance, how to write excellent commit messages in a version control system, how to communicate changes to the team, etc.

.
That would be awesome 馃槃

As a popular say states in spanish: 鈥淗asta al mejor chef se le queman los frijoles鈥.

Very important> Testing

Thanks

excellent

thanks
gracias

Functional and unit testing Functional testing
Come up with tests
It needs to guarantee your software鈥檚 optimal functionality

Technique 3: Unit Testing
Test the smallest pieces of code, it ties with continuous integration process

Manual testing: A group of developers manually starts testing the code鈥檚 functionality

Automated testing: For a more complex piece of software

System testing: Test things together, as a black box testing. Tests the overall functionality

Technique 4: Document it
Debriefing: Let your peers understand your code.
Become an expert communicator, know who is listening to you

The tests guarantee that the software has optimal functionality and there are several types of testing; per unit and per system, these can be manual or automatic

You can also 鈥渢ag鈥 your code. A 鈥渢ag鈥 is a snapshot of your
code at a certain time.
You can use tags to keep track of major progress in your
software, like milestones, iterations or changes in
requirements.

nice
hi