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: fix your bugs!
24/25En el desarrollo de software profesional es difícil darle prioridad a las pruebas. En especial en equipos pequeños, pues es donde se considera que no existe el tiempo suficiente para realizar los testings, sin embargo, estas empresas que están creciendo son las que más lo necesitan.
Buscar un balance entre el desarrollo y la escritura de pruebas es crucial. Intenta al menos que tu equipo dedique un 20% de tiempo en pruebas.
Términos importantes de pruebas de software
Es hora de hacer un repaso acerca de los términos y conceptos de pruebas de software en inglés.
| Concept | Context |
|---|---|
| Add more User Stories to fix your Bugs (Always be adjusting) | The time you need to fix your Bugs needs to be taken into consideration when estimating the length of your iterations. |
| Prioritize your User Stories | Prioritization is critical because you want to make sure you are doing the right thing on the project at all times. |
| Estimate again and learn from your data (VELOCITY) | Calculate your metrics and make sure you are readjusting after the iteration, your team may be working faster than you thought or more slowly. |
| The Lifecycle of a Bug | A tester finds the bug, the tester files a bug report, you create a story to fix the bug. Fix the bug, check the fix and verify that the fix works, and update your bug report. |
| Continuous Delivery–fix functional Bugs | Everything revolves around Customer-oriented functionality. Only fix what is broken, and you know what is broken because you have tests that fail. |
| Continuous Delivery–fix functional Bugs | Everything revolves around Customer-oriented functionality. Only fix what is broken, and you know what is broken because you have tests that fail. |
| Continuous Delivery as a Method for functionality | If it hurts, do it often, and it won’t hurt as much. |
Contribución creada por: Kevin Fiorentino.
Contribuições 0
Perguntas 0
Quer ver mais contribuições, perguntas e respostas da comunidade?