Software de alta calidad

Transcript

1. http://images.meredith.com/wood/images/p_411_1_1.gif Prácticas de desarrollo de software de alta calidad
2. <me>
3. Ingenierio de Software ex Crowd Interactive / MagmaLabs / FreeAgent Software Promotor del FLOSS Amante del Heavy Metal y la cerveza Instructor de Ruby on Rails en Platzi Anfitrión de la comunidad RubyGDL Fundador de elbuencodigo.com Fan de Gregory Sallust
4. </me>
5. http://cwebhealth.com/wp-content/uploads/2013/12/need-want-like-keys- showing-craving-and-desire_GyMuC-vu-702x336.jpg REQUERIMIENTOS
6. Entregar el software correcto
7. Specification by example
8. “Es un enfoque colaborativo para definir requetimientos y pruebas funcionales orientadas al negocio para productos de software con base en capturar e ilustrar los requerimientos usando ejemplos reales en lugar de sentencias abstractas”
9. Traducimos esto:
10. http://www.pmscs.net/images/Client.png Quiero que mi sistema tenga un Login de usuarios
11. En Esto:
12. Feature: Login In order to use the application As a user I want to be able to login Scenario: with invalid credentials Given I visit the / page And I have entered demo as my username And I have entered demo1234 as my password When I press Sign in Then I will be shown a message error Scenario: with valid credentials Given I have created an account in the past And I visit the /events page And I have entered demo as my username And I have entered demo1234 as my password When I press Sign in Then I will be redirected to events page
13. Gherkin!
14. “Es un lenguaje de dominio específico, leíble desde el lago de negocios que permite describir el funcionamiento del software sin detallar cómo será implementado”
15. Ya que Tenemos Lo que necesitamos
16. Manejo del proyecto http://www.targetprocess.com/blog/wp-content/uploads/2014/06/Kanban-with-time.jpg
17. “Una holística y flexicle estrategia de desarrollo de producto donde un equipo de desarrollo trabaja como una unidad para alcanzar un objetivo común "
18. Tres roles: http://braintrustgroup.com/assets/2012/09/SM-TM-PO-3pigs-01.png
19. Team Members: hacen las cosas
20. Product Owners: Representan la voz del cliente
21. Scrum master: Se asegura de que todo marche sobre ruedas
22. Product backlog
23. “Una comprensible lista de tareas, expresadas en orden de importancia para el negocio y cuánto valor aportan al mismo”
24. Herramientas
25. Sistema de Control de Versiones http://blog.laaz.org/tech/wp-content/uploads/2011/08/git-tree.png
26. “Un sistema que guarda los cambios hechos a un archivo o conjunto de archivos a través del tiempo”
27. Herramientas
28. Pruebas http://venturebeat.com/wp-
29. Pruebas unitarias
30. “Una metodología de pruebas de software en la que las unidades individuales de código son probadas para determinar si son aptas para ser utilizadas”
31. Herramientas
32. class User < ActiveRecord::Base # Método que prueba si un usuario tiene una cuenta de HackerGarage def has_hackergarare_account? !!self. email.match(/@hackergarage.mx$/) end end
33. require 'rails_helper' describe User do let(:user_with_hackergarage_account) { User.create email: 'demo@hackergarage.mx' } let(:user_with_gmail_account) { User.create email: 'demo@gmail.com' } describe '.has_hackergarage_account?' do it 'returns true when email ends with "@hackergarage.mx"' do expect( user_with_hackergarage_account.has_magmalabs_account? ).to be true end it 'returns false when email ends with "other domain"' do expect( user_with_gmail_account.has_hackergarage_account? ).to be false end end end
35. Pruebas de Integración
36. “La fase de pruebas de software en la cual las unidades individuales se combinan y prueban como un grupo”
37. Herramientas
38. Desarrollo basado En comportamiento
39. “Un método de pruebas en el que se utilizan ejemplos para describir el comportamiento de la aplicación o el comportamiento de la misma”
40. ¿Recuerdan esto?
41. Feature: Login In order to use the application As a user I want to be able to login Scenario: with invalid credentials Given I visit the / page And I have entered demo as my username And I have entered demo1234 as my password When I press Sign in Then I will be shown a message error Scenario: with valid credentials Given I have created an account in the past And I visit the /events page And I have entered demo as my username And I have entered demo1234 as my password When I press Sign in Then I will be redirected to events page
42. ¡Se puede convertir en código!
43. Feature: Login In order to use the application As a user I want to be able to login Scenario: with invalid credentials Given I visit the / page And I have entered demo as my username And I have entered demo1234 as my password When I press Sign in Then I will be shown a message error Scenario: with valid credentials Given I have created an account in the past And I visit the /events page And I have entered demo as my username And I have entered demo1234 as my password When I press Sign in Then I will be redirected to events page
44. Given(/^I visit the (.*) page$/) do |page| visit page end
45. Feature: Login In order to use the application As a user I want to be able to login Scenario: with invalid credentials Given I visit the / page And I have entered demo as my username And I have entered demo1234 as my password When I press Sign in Then I will be shown a message error Scenario: with valid credentials Given I have created an account in the past And I visit the /events page And I have entered demo as my username And I have entered demo1234 as my password When I press Sign in Then I will be redirected to events page
46. And(/^I have entered (.*) as my username$/) do |username| fill_in 'user[login]', with: username end And(/^I have entered (.*) as my password$/) do |password| fill_in 'user[password]', with: password end
47. Feature: Login In order to use the application As a user I want to be able to login Scenario: with invalid credentials Given I visit the / page And I have entered demo as my username And I have entered demo1234 as my password When I press Sign in Then I will be shown a message error Scenario: with valid credentials Given I have created an account in the past And I visit the /events page And I have entered demo as my username And I have entered demo1234 as my password When I press Sign in Then I will be redirected to events page
48. Given(/^I have created an account in the past$/) do @user = FactoryGirl.create :user, username: 'demo', password: 'demo1234' End Then(/^I will be shown a message error$/) do expect(page).to have_content 'Invalid login or password.' end When(/^I press Sign in$/) do click_button 'Sign in' end Then(/^I will be redirected to home page$/) do expect(page).to have_content 'Login successful' end Then(/^I will be redirected to (.*) page$/) do |url| path = URI.parse(current_url).path expect(path).to match "/#{url}" end
49. Herramientas
50. Pruebas multinavegador
51. Tools
52. Lanzamiento http://i.dawn.com/primary/2013/06/51b99d8da936d.jpg
53. Platform as A Service (PaaS)
54. Servicios
55. Virtual Private Servers (VPS)
56. Servicios
57. Herramientas
58. role :demo, %w{example.com example.org example.net} task :uptime do on roles(:demo), in: :parallel do |host| uptime = capture(:uptime) puts "#{host.hostname} reports: #{uptime}" end end
59. Hacer un deploy es tán fácil como correr:
60. cap production deploy
61. Continuos integration/ delivery/ deployment
62. “Continuous Integration is the practice of merging development work with a Master/Trunk/Mainline branch constantly so that you can test changes, and test that changes work with other changes” http://blog.assembla.com/AssemblaBlog/tabid/12618/bid/92411/Continu ous-Delivery-vs-Continuous-Deployment-vs-Continuous-Integration-Wait- huh.aspx
63. “Continuous Delivery is the continual delivery of code to an environment once the developer feels the code is ready to ship.” http://blog.assembla.com/AssemblaBlog/tabid/12618/bid/92411/Continu ous-Delivery-vs-Continuous-Deployment-vs-Continuous-Integration-Wait- huh.aspx
64. “Continuous Deployment is the deployment or release of code to Production as soon as it is ready” http://blog.assembla.com/AssemblaBlog/tabid/12618/bid/92411/Continu ous-Delivery-vs-Continuous-Deployment-vs-Continuous-Integration-Wait- huh.aspx
65. Herramientas
66. Calidad de código http://www.pts-qc.com/images/AUDITING.jpg
67. Code review
68. Herramientas
70. Métricas de código
71. Herramientas
73. Analizadores sintácticos
74. Rubocop CSSLinter JSHint Hound CI Herramientas
75. scss_files: "**/*.scss" linters: BangFormat: enabled: true space_before_bang: true space_after_bang: false BorderZero: enabled: true convention: zero # or `none` ColorKeyword: enabled: true ColorVariable: enabled: true Comment: enabled: true DebugStatement: enabled: true
77. Mantenimiento http://www.mengsolutions.com.au/wp-
78. Reporte de errores
79. Herramientas
81. Disponibilidad del sitio
82. Herramientas
84. Hasta ahora sólo he hablado sobre herramientas y metodologías
85. Pero lo más Importante es
86. La gente
87. “El software de alta calidad es creado por personas que se preocupan y aman su trabajo”
88. ¿Preguntas?
89. ¡Gracias! me@ferperales.net