A√ļn no tienes acceso a esta clase

Crea una cuenta y contin√ļa viendo este curso

Functional and unit testing

15/27
Recursos

In this lesson you will learn: Functional Testing
Technique #3 - Always exercise your code - unit testing,
Technique #4 - Let your peers understand your code - Document it!!

Challenge: using your knowledge of Defensive Development, answer this quiz.

Aportes 7

Preguntas 0

Ordenar por:

¬ŅQuieres ver m√°s aportes, preguntas y respuestas de la comunidad? Crea una cuenta 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’s 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’s 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

This course is great, I’d 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 ūüėĄ

You can also ‚Äútag‚ÄĚ your code. A ‚Äútag‚ÄĚ 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.

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