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,
Handle accidents when building the code and what CI means
17/25Al desarrollar software muchas integraciones pueden fallar y es importante detectar estos bugs a tiempo para no complicar más la entrega del proyecto o la manera de trabajar de tu equipo en la empresa.
Manejar accidentes al construir el código.
Imagina que has terminado tu trabajo y funciona perfectamente en tu ordenador. Envías los cambios al repositorio, pero tus compañeros de equipo comienzan a tener problemas con esa nueva funcionalidad.
- There are many things that can go wrong with software development.
- Think of examples of problems that might arise when developing new software.
- Do you have the same problems when you are working with small or big teams?
- How’s your Continuous Integration?
Qué es la integración contínua (CI)
La Integración Continua es una técnica para dar garantías y reducir el impacto de conflictos en el código de tu proyecto.
- Principles of CI:
- Continuously submitting working, runnable software into the source that will be built and tested.
- Using automation to enable source control to build and test the latest version of your code submitted by the developers.
- Continuous Integration tools run your tests as soon as you submit your code.
- Source control emails the developers last involved in conflicts that appear when submitting.
- Continuous Integration wraps version control compilation and testing into a single repeatable process.
- Source Control guarantees the impact reduction of conflicts.
- Avoid Merge Hell.
- Fix bugs quickly, testable build.
- Ensure Ownership.
Trabajar con Integración Continua optimiza los tiempos de aparición y resolución de bugs, además de mejorar la comunicación con tu equipo de trabajo que desarrolla software.
Contribución creada por: Kevin Fiorentino.`
Contribuições 0
Perguntas 0
Quer ver mais contribuições, perguntas e respostas da comunidade?