Introduction
Welcome to this Course for Developers in English
Communicate with your customer accurately
Customer-oriented requirements
How iteration cycles work
Planning considering priorities
Review: communicate with your customer accurately
Understand your customer and the requirements
Prioritizing requirements
Backlog and Milestone 1.0
Organize your tasks!
Organizing your time into user stories and tasks
Stand-up meetings, analyze and design
Review: organize your tasks!
Create deliverable design
Creating deliverable design
Refactoring, meetings and release
Protect your very valuable software
Understanding the principles of defensive development
Functional and unit testing
Review: protect your very valuable software
Understanding Continuous Integration (CI) and testing
Types of software testing
Handle accidents when building the code and what CI means
Test your Software!
TDD Test-Driven Development
Review: test your software!
Be ready for the end
Prepare for the next iteration
End an iteration
Fix your bugs!
Handle bugs to fit your process
Continuous integration test delivery method
Review: fix your bugs!
Conclusion
We've come to an end!
Expert Mentorship
Você não tem acesso a esta aula
Continue aprendendo! Junte-se e comece a impulsionar sua carreira
Se você já tem uma conta,
Review: test your software!
19/25Revisemos 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.
Contribuições 0
Perguntas 0
Quer ver mais contribuições, perguntas e respostas da comunidade?